Packaging and Python 2

[dstufft (Donald Stufft)]

@njs

BTW, I expect that Python 2 packaging will run into another problem in a year or two. At some point, package maintainers will start taking for granted that python 3 is the only python. Right now, Python-Requires: gives a way for packages to opt-out of python 2 support, but we might need to switch to an opt-in model, or else have PyPI become gradually unusable for the py2 laggards.

It’s probably better to solve this at the build tool level. Tools like setuptools, flit, etc could start defaulting to having a 3.x only Requires-Python and require someone to explicitly set Requires-Python to regain 2.x support. With an appropriate deprecation period and backwards compatibility management for that particular project.

I think PyPI works best remaining relatively neutral about the files it’s hosting.