-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Timeline for dropping Python 2 support #6580
Comments
Dropped in #6601. |
@robertnishihara is it ok to pin this issue (or at least a note that we have officially dropped Py3) until the next release? It was really only visible for 7 days (and during holiday season). The note is helpful for developers/committers to know so that they can take advantage of features such as f-strings. |
@richardliaw done. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the end of Python 2 nearing at a rapid pace (https://pythonclock.org/), we are looking into dropping Python 2 support for new releases after Jan 1, 2020. The main benefit would be that quite a bit of our code could be simplified (especially serialization). Several of the new features we're developing (Ray serve and the Ray dashboard) already don't support Python 2.
If you have a project using Ray/planning to use Ray that crucially depends on Python 2 support for new releases, please let us know about it. See also https://python3statement.org/.
The text was updated successfully, but these errors were encountered: