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

Python 2 roadmap #2800

Juanlu001 opened this Issue Jan 17, 2019 · 2 comments


None yet
3 participants
Copy link

Juanlu001 commented Jan 17, 2019

As you might have heard, Python 2 is EOL in about 11 months. I wonder what is the roadmap of Cython regarding Python 2 support, because most core scientific Python projects have already explicited theirs.

In particular, I guess dropping Python 2 support would help fixing some cygdb bugs which in my opinion make using Cython a bit more painful than it should.


This comment has been minimized.

Copy link

robertwb commented Jan 17, 2019


This comment has been minimized.

Copy link

scoder commented Jan 23, 2019

I agree with what Robert said, also regarding a discussion on the list.

To add a bit to that, CPython 3.8 is scheduled for October 2019, and that seems like the point of decision to me. I think some users might appreciate it if we could get a Cython release out then that supports it as well as Python 2.7, so that they could continue to use that release as long as they feel like it. But I would personally not mind having 0.29 be the last Py2 compatible release, or 3.0. It's not like what's been released will magically start failing on January 1st next year. And I probably wouldn't object to making a bug fix release for that last Py2 release series if someone backports a fix that we make in a future version.

I think the main question is really: should we still add Py3.8 to the current list of supported Py2+ versions or not.

I don't see a future Cython release support Python 3.9+ and still carry around Py2.7 cruft.

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