Ned Deily added the comment: 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. ---------- nosy: +ncoghlan priority: normal -> release blocker _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28092> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
