-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
FIX: support python311 #3762
FIX: support python311 #3762
Conversation
In 18b5dd68c6b616257ae243c0b6bb965ffc885a23 / python/cpython#31530 / https://bugs.python.org/issue46836 the _frame struct was moved to an internal header, however the public API is primarily read-only.
for more information, see https://pre-commit.ci
This isn't the right fix. The proper fix is just to not access the member of PyFrameObject directly anymore, but instead use the new limited C-API getters for newer versions of Python. (I don't think we write to any of the _frame fields so the new read only API should be just fine). There are some other breaking changes for Python 3.11 that need to be fixed as well such as in: #3694 update : fixed link |
@tacaswell Can you paste the full error if this include is missing? I suspect it's just from f_back in error_string() that we need to make use the new API? |
Re-running just the g++ gives
so I think this is the relevant part of the log. |
@tacaswell I have added the proper changes to #3694. Can you verify that this solves the issue? |
Closed in favor of not using private API via #3694 . |
In 18b5dd68c6b616257ae243c0b6bb965ffc885a23 / python/cpython#31530 / https://bugs.python.org/issue46836 the _frame struct was moved to an internal header, however the public API is primarily read-only.
I am not sure that this is the correct fix, but it gets scipy to compile again!
Description
Suggested changelog entry: