Updates to PEP-513
Hi all, Based on recent discussions, I'm proposing the following update to PEP 513: https://github.com/pypa/manylinux/pull/31/files The changes to the text are: * Remove the UCS-4 requirement in favor of pip/wheel's new SOABI support. * Mandate that manylinux1 extensions not link against libpythonX.Y.so.1, for the complicated compatibility-related reasons that were discussed on list. * Update link for the docker images to their new PyPA home. Comments welcome, of course. I haven't sent this to the PEP editors yet, because I'm not sure if there's any particular ceremony needed for changing the semantics of a PEP that's already been pronounced upon? -n -- Nathaniel J. Smith -- https://vorpus.org
On 9 February 2016 at 11:36, Nathaniel Smith
Hi all,
Based on recent discussions, I'm proposing the following update to PEP 513:
https://github.com/pypa/manylinux/pull/31/files
The changes to the text are:
* Remove the UCS-4 requirement in favor of pip/wheel's new SOABI support. * Mandate that manylinux1 extensions not link against libpythonX.Y.so.1, for the complicated compatibility-related reasons that were discussed on list. * Update link for the docker images to their new PyPA home.
+1 from me.
Comments welcome, of course.
I haven't sent this to the PEP editors yet, because I'm not sure if there's any particular ceremony needed for changing the semantics of a PEP that's already been pronounced upon?
No particular ceremony, as I'm treating these as bugs found by working on the reference implementation (in this case, the Docker build environment). Finding spec defects after approval is actually a pretty normal occurrence for PEPs targeting the CPython reference implementation, as some flaws only become apparent once you put something to the test of implementation (as happened here). Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (2)
-
Nathaniel Smith
-
Nick Coghlan