-
Notifications
You must be signed in to change notification settings - Fork 247
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
Consider releasing a new greenlet 1.1.3 version compatible with Python 3.11 #305
Comments
We wrote the PR #306 which adds Python 3.11 support to greenlet 1.x. |
Downstream patch in Fedora: https://src.fedoraproject.org/rpms/python-greenlet/pull-request/3 |
@jamadden: What do you think of this issue? It seems like @ssbarnea also wants a greenlet compatible with Python 3.11: #306 (comment) |
greenlet, a dependency of SQLAlchemy, doesn't support Python 3.11, yet. See <python-greenlet/greenlet#305>.
Would be great to get a release out, as there's been some stability issues with Python 3.11 beta so it's very important to test it, and this is blocking other projects testing 3.11 that depend on greenlet. See: Thank you! |
Python 3.11 rc1 will be released on August 8th. It would be great if we can have the Python 3.11 support at the same time. |
Would really appreciate a fix here; |
#306 has been merged and 1.1.3 released to PyPI. |
The current main branch is a new greenlet 2.0 version which has a different API than greenlet 1.x and is written in C++. Shipping greenlet 2.0 alpha in the future Fedora 37 scheduled for next October (2022) sounds risky. We (Fedora) would like to upgrade Python to Python 3.11 but keep greenlet 1.x.
Would you be open to consider releasing a new greenlet 1.1.3 version which would be compatible with Python 3.11?
We prepared a PR on top on the 1.1.2 version to add Python 3.11 support.
Python 3.11 final version is also scheduled next October (2022): https://peps.python.org/pep-0664/#schedule
See also the issue #303: "Schedule for a beta release of greenlet 2.0?"
The text was updated successfully, but these errors were encountered: