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.7 #1730

Closed
jaraco opened this Issue Aug 16, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@jaraco
Member

jaraco commented Aug 16, 2018

  • I'm submitting a ...
  • bug report
  • feature request
  • question about the decisions made in the repository
  • Do you want to request a feature or report a bug?

See above.

I think it's about time to drop support for Python 2.7. This project has made many stable updates and maintained Python 2.7 support for a very long time, but many of the issues with this project stem from unicode handling issues in patterns developed very early in the Python 2 to 3 transition, patterns that today create a bimorphism of bytes on Python 2 and unicode on Python 3 that pervades the code base.

I propose we cut a backward-incompatible release dropping support for Python 2.7, but maintain a py27-maintenance branch against which critical bugfixes may be applied, but for general development in master, rely on Python 3.4+.

@webknjaz

This comment has been minimized.

Member

webknjaz commented Aug 17, 2018

jaraco added a commit that referenced this issue Sep 1, 2018

jaraco added a commit that referenced this issue Sep 1, 2018

jaraco added a commit to cherrypy/python3statement.github.io that referenced this issue Sep 1, 2018

jaraco added a commit to cherrypy/python3statement.github.io that referenced this issue Sep 1, 2018

jaraco added a commit that referenced this issue Sep 1, 2018

Carreau added a commit to python3statement/python3statement.github.io that referenced this issue Sep 1, 2018

jaraco added a commit that referenced this issue Sep 1, 2018

jaraco added a commit that referenced this issue Sep 1, 2018

@jaraco

This comment has been minimized.

Member

jaraco commented Sep 1, 2018

I honestly can't figure out why Travis isn't running tests on older Pythons. I'll leave that as an exercise for later.

@webknjaz

This comment has been minimized.

Member

webknjaz commented Sep 1, 2018

@jaraco there's if-clauses, which you're probably hitting. You can always trigger manual tests run in Travis directly. We're running much more jobs on daily cron builds and API triggers (which also count as manual runs)

@jaraco jaraco closed this in 63551ec Sep 1, 2018

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