Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Python 2 roadmap #2800
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.
We don't have a specific roadmap, but given that we're a low-level dependency we do have a history of supporting Python versions long after EOL. We are working on changing the default language level to be 3 with the next release. This is a good question for the list. (It would be good to fix the cygdb bugs regardless, only fixing them on Python 3 would be reasonable.)…
On Thu, Jan 17, 2019 at 10:14 AM Juan Luis Cano Rodríguez < ***@***.***> wrote: As you might have heard, Python 2 is EOL in about 11 months <https://pythonclock.org/>. I wonder what is the roadmap of Cython regarding Python 2 support, because most core scientific Python projects have already explicited theirs <https://python3statement.org/>. In particular, I guess dropping Python 2 support would help fixing some cygdb bugs <https://github.com/cython/cython/issues?utf8=%E2%9C%93&q=is%3Aopen+cygdb> which in my opinion make using Cython a bit more painful than it should. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2800>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAdqgW-ODxCHQgMo0mOuzoluoTQRnocUks5vED8SgaJpZM4aEwjw> .
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.