PEP 571: Manylinux2

[markrwilliams]

manylinux1 needs an update. This is an attempt at a successor.

See pypa/manylinux#152, pypa/auditwheel#88, and pypa/pip#5008.

[brettcannon]

Has this been discussed yet on distutils-sig or pypa-dev?

[markrwilliams]

@brettcannon I have just sent an email to distutils-sig. I opened this PR so that GitHub would associate it with PRs I've opened against pypa/manylinux, pypa/auditwheel, and pypa/pip as a kind of umbrella for that work.

[brettcannon]

Fair enough, but we typically don't accept PEPs into the repo that have not had at least one round of discussion on a public mailing list first (this is when we suggest people do the work on their personal fork first, then send the PR).

Because of that I'm going to close this PR for now, but I can re-open it once the PEP has gone through more public review.

[ofek]

@brettcannon We should consider this an escalated issue due to https://news.ycombinator.com/item?id=16277806. This week all manylinux1 images will no longer be able to access GitHub.

cc @trishankatdatadog

[brettcannon]

@ofek Any escalation wouldn't be for here but for the people who will have to make the final decision of the PEP which would be distutils-sig.

[markrwilliams]

@ofek Thanks for your interest! My PEP has made it to the distutils-sig mailing list, so let's discuss it there:
https://mail.python.org/pipermail/distutils-sig/2018-February/031944.html

[njsmith]

@ofek It's not quite as bad as your comment makes it sounds – the GitHub change makes it more difficult to create the manylinux1 images, because they've relying on GitHub's lenient TLS policies to bootstrap themselves to a more secure setup. But users of the manylinux1 images are OK, because the curl and pythons we ship are all built using a modern openssl.

[ncoghlan]

Assigning to myself and reopening, since we've had an initial discussion on distutils-sig now :)