[Pyrex] Python 2.4 & Pyrex Compatibility Update

[Brandon King]

This e-mail seems as though it didn't make it on to pyrex mailing list,
so I'm forwarding it.

-Brandon King

Joseph C Roden wrote:

>
> On Wed Jul 20 23:54:15 CEST 2005, Brandon King wrote:
>
>>>     I was wondering what the status is on Pyrex compatibility with
>>> Python 2.4? I kept having trouble getting 'python2.4 setup.py  install'
>>> to work with a package that tries to build a .pyx file. Is this 
>>> still a
>>> problem?
>>
>
> On Thu Jul 21 02:02:26 CEST 2005, Grant McDonald wrote:
>
>> I don't have any problems using the following setup.py with python 
>> 2.4.1:
>>
>> # setup.py
>> import distutils
>> from distutils.core import setup, Extension
>> import os,sys
>>
>> os.system("python C:\Python24\Scripts\pyrexc.py vm8.pyx")
>>
>> setup(name = "Version Manager 8 DTK Interface",
>>
>>    (...snip...)
>>
>> Can you send the setup.py that is giving you a problem?
>
>
> The above solution is one workaround that I've seen people suggest,
> i.e. manually executing pyrexc.py on your pyrex modules prior to
> calling setup.  I've seen Brandon's setup.py and it does not call pyrexc
> explicitly, but lets distutils do that work, which gets tripped up on a
> build_ext.swig_sources argument mismatch.
>
> I found that an earlier post directly discussed this problem and offered
> a patch that solves Brandon's setup.py problem.
>
> On 29 Dec 2004 at 3:12, Bob Ippolito wrote:
>
>> Python 2.4's distutils changed the call signature of
>> build_ext.swig_sources to include an extra extension argument.
>
>
> For full details of the earlier posting, including John's (sjmachin's)
> suggested patch, see:
>
>   http://lists.copyleft.no/pipermail/pyrex/2004-December/001084.html
>
> I wanted to run the test suite to confirm that the patch works more
> generally (I assume it does), but I got tripped up on the Mac OS X
> FSCatalogInfo.finderInfo and _Filemodule.c issue, so I could not run
> the tests.
>
> Nonetheless, if the patch is working as it seems it is, I hope it 
> will be
> added to the next distribution.  When might that be available?  I've
> heard people suggest that others wait to upgrade to Python 2.4
> because Pyrex is "not compatible" with Python 2.4.  Now at least
> we know this issue can be resolved with a tiny patch.
>
> Joe
>
>
>