➜

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 ned.deily
Recipients benjamin.peterson, lukasz.langa, martin.panter, ncoghlan, ned.deily, steven.daprano, tds333
Date 2016-09-12.08:35:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473669343.47.0.0877516673021.issue28092@psf.upfronthosting.co.za>
In-reply-to
Content 
Do we know for sure that the manylinux1 builds are affected by this, i.e. can someone try building manylinux1 for 3.6?

On the one hand, it is clear that many core developers would like to use these newer features of C, features that have been available for many years.  On the other, we may be breaking the "manylinux1" proposed standard and force a move to a newer one, as well as directly impacting some users (such as Steven and one of our buildbots) using old setups.

Nick, as BDFL-Delegate for PEP 513, what do you think?  We need to resolve this issue before we can release b1.
History
Date User Action Args
2016-09-12 08:35:43ned.deilysetrecipients: + ned.deily, ncoghlan, tds333, benjamin.peterson, steven.daprano, lukasz.langa, martin.panter
2016-09-12 08:35:43ned.deilysetmessageid: <1473669343.47.0.0877516673021.issue28092@psf.upfronthosting.co.za>
2016-09-12 08:35:43ned.deilylinkissue28092 messages
2016-09-12 08:35:43ned.deilycreate