Skip to content

Conversation

@di
Copy link

@di di commented Oct 30, 2016

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 projects setup.py.

@gsnedders
Copy link
Member

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).

@di
Copy link
Author

di commented Oct 31, 2016

@gsnedders Thanks, it seems this PR is a bit premature then. Sorry for the noise!

@di di closed this Oct 31, 2016
@di di deleted the drop-py26 branch October 31, 2016 14:33
@gsnedders
Copy link
Member

@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!

@jdufresne
Copy link
Contributor

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

@gsnedders
Copy link
Member

The outcome of the discussion I had with @dstufft before was that:

  1. The next version will support 2.6 (it is almost certain to be 9.1)
  2. 9.x is likely to be the current major release until mid-2017
  3. It'd be ideal to keep supporting 2.6 until pip's support is finally dropped (e.g., in case of any last-minute security releases shortly before 10.0)

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.

@willkg willkg added this to the 1.0 milestone Oct 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants