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 Bob
Recipients Bob, doko, larry, mark.dickinson, mattip, meador.inge, python-dev, rkuska, steve.dower
Date 2015-03-24.20:11:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427227895.61.0.0554956111299.issue20160@psf.upfronthosting.co.za>
In-reply-to
Content
ok, forgive me for asking a newbe question ot two, but when you say 'fixed in nov 2014' are you refering to the release mentioned below or something else, possibly something that didn't make it into 2.7.9?  

I dont really understand what 'resync libffi with the upstream version' means, but I assume that if this is done my python-clang issue might be fixed?  So having a test is important, I'll see what I can do.

I'm working with the 2.7.9 release source, because I need a fix that can be dropped into the 2.7.9 official release folder so that people here can use python-clang. The source I have for 2.7.9 does appear to have the release below in it, including the changes to test_win32.py (which still passes with my fix)
History
Date User Action Args
2015-03-24 20:11:35Bobsetrecipients: + Bob, doko, mark.dickinson, larry, meador.inge, python-dev, mattip, steve.dower, rkuska
2015-03-24 20:11:35Bobsetmessageid: <1427227895.61.0.0554956111299.issue20160@psf.upfronthosting.co.za>
2015-03-24 20:11:35Boblinkissue20160 messages
2015-03-24 20:11:35Bobcreate