-
-
Notifications
You must be signed in to change notification settings - Fork 31.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
Py_FinalizeEx unconditionally exists in Py_LIMITED_API #79440
Comments
In application compiled with
#define Py_LIMITED_API 0x03040000
this method was used
Py_FinalizeEx() Tested application with: Result: (X) The procedure entry point Py_FinalizeEx could not be located Expected Result: Rebuilding, after replacing Py_FinalizeEx(void) with Py_Finalize(void): Suggested resolution: #if !defined(Py_LIMITED_API) || Py_LIMITED_API+0 >= 0x03060000
PyAPI_FUNC(int) Py_FinalizeEx(void);
#endif |
I added the Py_FinalizeEx API in bpo-5319, but was relying on input from others about dealing with Py_LIMITED_API. After reading the documentation <https://docs.python.org/3.6/c-api/stable.html\>, I now see that the function would be considered part of the limited API because its documentation doesn’t say otherwise. So Arthur’s resolution is correct. |
Py_FinalizeEx()
toPy_LIMITED_API >= 0x03060000
#10620Py_FinalizeEx()
toPy_LIMITED_API >= 0x03060000
. (GH-10620) #11268Py_FinalizeEx()
toPy_LIMITED_API >= 0x03060000
. (GH-10620) #11269Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: