➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients Arfrever, djc, doko, meador.inge, ronaldoussoren
Date 2013-02-06.08:01:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1360137709.23.0.126119999918.issue17136@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't know how the main copy of libffi in the CPython tree is updated, and if it is a straight copy of the upstream release. Given the mercurial log I'd guess that Modules/_ctypes/libffi is libffi 3.0.11 with a small patch in Modules/_ctypes/libffi.diff.

As Arfrever notes libffi_osx is used on OSX only, and that version is a fork of libffi shared with PyObjC (that is, I try to update the copy in the CPython tree whenever I have to update the copy for PyObjC). 

I agree that the issue with libffi should be fixed upstream first,  otherwise it would get harder and harder to import new upstream versions.
History
Date User Action Args
2013-02-06 08:01:49ronaldoussorensetrecipients: + ronaldoussoren, doko, djc, Arfrever, meador.inge
2013-02-06 08:01:49ronaldoussorensetmessageid: <1360137709.23.0.126119999918.issue17136@psf.upfronthosting.co.za>
2013-02-06 08:01:49ronaldoussorenlinkissue17136 messages
2013-02-06 08:01:48ronaldoussorencreate