-
Notifications
You must be signed in to change notification settings - Fork 614
Support for Python 3.12 #514
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
Comments
Hi @xqt, we will take a look at this, thank you. |
@xqt, python 3.12 is unavailable in official python ftp: https://www.python.org/ftp/python/ |
Probably will be added late October after the launch of Python 3.11.0. |
Is Python 3.12 now available? @panticmilos could you give some context? |
Hi @EwoutH, I thought @vsafonkin explained the situation. I will reopen it till we add it. |
I think it will be better to keep this issue as opened until we add python 3.12 support. |
For the record 3.12a1 has been released: https://www.python.org/ftp/python/3.12.0/ |
Ping! Did this fall into oblivion? |
Hello @kxrob |
In the meantime, https://github.com/deadsnakes/action can be used to test on Python 3.12. |
Could we pin this issue? That makes it easier to find and keep track of. |
Hi all! |
Python 3.12 release candidates are available, version 3.12 has been available in GitHub runners for almost a year: actions/setup-python#514
Python 3.12 release candidates are available, and version 3.12 has been available in GitHub runners for almost a year: actions/setup-python#514
Python 3.12 release candidates are available, and version 3.12 has been available in GitHub runners for almost a year: actions/setup-python#514
Python 3.12 release candidates are available, and version 3.12 has been available in GitHub runners for almost a year: actions/setup-python#514
Description:
Please add support for Python 3.12
Justification:
Python 3.12 is in alpha state. It should be able to test code with Python 3.12 with github action. Please add that release to versions-manifest.json. Thank you.
The text was updated successfully, but these errors were encountered: