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 gregory.p.smith
Recipients Arfrever, benjamin.peterson, doko, eric.araujo, georg.brandl, gregory.p.smith, koobs, larry, python-dev, ronaldoussoren
Date 2013-04-30.06:37:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367303861.94.0.878823490799.issue17192@psf.upfronthosting.co.za>
In-reply-to
Content
it _looks_ like the libffi updates i put in 3.2, 3.3 and default (3.4) are messed up with some changes missing in 3.2 and more missing in 3.3 and 3.4.  (i'm comparing vs upstream 3.0.13 <-> 2.7 <-> 3.2 <-> 3.3 <-> 3.4).

i blame the mess of merging that was required by hg due to the plethora of versions of libffi we had in different states in 2.7, 3.2 and 3.3+ before i did the update.  i'm fixing it now.
History
Date User Action Args
2013-04-30 06:37:42gregory.p.smithsetrecipients: + gregory.p.smith, georg.brandl, doko, ronaldoussoren, larry, benjamin.peterson, eric.araujo, Arfrever, python-dev, koobs
2013-04-30 06:37:41gregory.p.smithsetmessageid: <1367303861.94.0.878823490799.issue17192@psf.upfronthosting.co.za>
2013-04-30 06:37:41gregory.p.smithlinkissue17192 messages
2013-04-30 06:37:41gregory.p.smithcreate