[Python-Dev] Maintaining old releases

M.-A. Lemburg mal at egenix.com
Wed Aug 13 12:56:06 CEST 2008

On 2008-08-13 04:57, Guido van Rossum wrote:
>> And there's a reason for this slow uptake of Python 2.5: as more
>> and more servers run 64-bit OSes, the Py_ssize_t changes cause
>> serious trouble with Python C extensions that were not updated
>> by their authors.
> I'm not sure what that has to do with anything. The older releases
> have *worse* support for 64-bit platforms!

This is one of the reasons why porting applications from 2.4 to 2.5
takes longer than e.g. moving from 2.3 to 2.4.

Python 2.4 works just fine on 64-bit platforms and so do the C
extensions that were written for it. Moving to 2.5 you often find
that those C extensions do not support the new Py_ssize_t types
and thus generate segfaults.

As a result, you either have to start using a different C extension,
patch the extension, stay with Python 2.4 or use a custom Python
interpreter that is patched always map Py_ssize_t to int.

The move from 2.5 to 2.6 will be a lot easier and uptake a lot

Marc-Andre Lemburg

Professional Python Services directly from the Source  (#1, Aug 13 2008)
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/

:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::

    eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
     D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
            Registered at Amtsgericht Duesseldorf: HRB 46611

More information about the Python-Dev mailing list