Conversation
|
As a package vendored by pip, we're not going to drop support till pip does to avoid pip having to maintain a fork, currently planned for pip 10.0 (pypa/pip#3955). |
|
@gsnedders Thanks, it seems this PR is a bit premature then. Sorry for the noise! |
|
@di I'm more than happy to keep the PR open, because it saves duplicating the work in the probably relatively near future, and I'm grateful for you doing it! It sounds like pip 9.0 is nearer than I expected, so probably nearer to being able to land this than I expected! |
|
Should this PR be reconsidered now that pip has officially deprecated 2.6 and will be dropping it in the next version? https://mail.python.org/pipermail/distutils-sig/2016-November/029785.html |
|
The outcome of the discussion I had with @dstufft before was that:
Given the relatively small gains from dropping 2.6 (as I think the PR shows, the majority of the gains are in being able to finally use set and dict literals), I'm in no rush and happy to wait for 10.0 to ship. |
Yesterday marks 3 years since the last release of Python 2.6! 🎉
To celebrate, I'm attempting to drop support for it from 156 prominent Python packages (one for every week it's past end-of-life)--including this one!
I've tried my best to remove as much 2.6-specific cruft as I can, but at the very least, this PR will remove the
'Programming Language :: Python :: 2.6'trove classifier from this projectssetup.py.