-
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
py311 issues with const correctness #301
Comments
There was a second class of casting issues that I missed on the first read of the errors. |
This is fixed by python/cpython#92951 |
This change will be part of Python 3.11 beta2 scheduled at next week (Monday, 2022-05-30). |
This is nothing to do in the greenlet side, so I suggest closing the issue. See my follow-up issue: #303 "Schedule for a beta release of greenlet 2.0?" |
See also #302 (no longer needed). |
This was also fixed upstream. |
I'm opening a different issue from #288 because those were all of the type "a struct changed" where as this is related to how casting is done and the tracking of const correctness.
python/cpython#91959 changed how casting was done internally to CPython to silence compiler errors. However by moving to the new method of casting, the compiler is now detecting that
const
is being discarded.Per python/cpython#91959 (comment)
I think the fix is to add
const_cast
in greenlet before calling into the CPython apis as needed.compiler errors folded:
The text was updated successfully, but these errors were encountered: