New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop support for Python 2.6 #1607

Closed
jaraco opened this Issue Jul 8, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@jaraco
Member

jaraco commented Jul 8, 2017

Beginning with 705eea1, the tests started failing... because the updated version of portend dropped support for Python 2.6.

Additionally, packaging tools and other foundational packages will be dropping support for Python 2.6 soon too.

It's time for CherryPy to do the same.

@jaraco jaraco self-assigned this Jul 8, 2017

@jaraco jaraco closed this in 5af46f1 Jul 8, 2017

@webknjaz

This comment has been minimized.

Show comment
Hide comment
@webknjaz

webknjaz Jul 8, 2017

Member

There's a lot more legacy hacks yet to clean up. Shall we keep this issue open or create a new one for this?

Member

webknjaz commented Jul 8, 2017

There's a lot more legacy hacks yet to clean up. Shall we keep this issue open or create a new one for this?

@webknjaz

This comment has been minimized.

Show comment
Hide comment
@webknjaz

webknjaz Jul 8, 2017

Member

Should we do the same to cheroot?

Member

webknjaz commented Jul 8, 2017

Should we do the same to cheroot?

@jaraco

This comment has been minimized.

Show comment
Hide comment
@jaraco

jaraco Jul 8, 2017

Member

I figure the legacy cleanup can happen at leisure. There are still pre-2.6 cruft in there that can go too. I don't think it needs to be ticketed.

We can do the same for cheroot soonish. No rush.

Member

jaraco commented Jul 8, 2017

I figure the legacy cleanup can happen at leisure. There are still pre-2.6 cruft in there that can go too. I don't think it needs to be ticketed.

We can do the same for cheroot soonish. No rush.

@webknjaz

This comment has been minimized.

Show comment
Hide comment
@webknjaz

webknjaz Jul 9, 2017

Member

Alright, what about 3.2? It's also problematic. Are we going to drop it as well?

Member

webknjaz commented Jul 9, 2017

Alright, what about 3.2? It's also problematic. Are we going to drop it as well?

@webknjaz

This comment has been minimized.

Show comment
Hide comment
@webknjaz

webknjaz Jul 9, 2017

Member

Oh.. And in setup.py we even claim support for 3.1, which I doubt anyone uses now as well.

Member

webknjaz commented Jul 9, 2017

Oh.. And in setup.py we even claim support for 3.1, which I doubt anyone uses now as well.

@jaraco

This comment has been minimized.

Show comment
Hide comment
@jaraco

jaraco Jul 9, 2017

Member

I'm not sure how Python 3.2 is problemmatic. If someone makes the case for dropping support, I imagine we could consider it. One area where there's still high demand for Python 3.2 support is in PyPy versions, though later versions have more modern interpreter support, so that's probably a non-issue.

Member

jaraco commented Jul 9, 2017

I'm not sure how Python 3.2 is problemmatic. If someone makes the case for dropping support, I imagine we could consider it. One area where there's still high demand for Python 3.2 support is in PyPy versions, though later versions have more modern interpreter support, so that's probably a non-issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment