-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
python3.lib in Python3.9.0 Windows distribution does not contain PyObject_CallNoArgs symbol #86581
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
I'm unsure if this is a packaging error or a misunderstanding by me. I'm trying to link a binary on windows with Py_LIMITED_API set. According to https://www.python.org/dev/peps/pep-0384/#linkage I _think_ I'm supposed to be linking against python3.lib (instead of python39.lib). However my build fails because the PyObject_CallNoArgs symbol is not present in python3.lib I see that the symbol is indeed present in python39.lib Is this a misunderstanding on my part? I was under the impression that python3.lib will only contain symbols available in the limited api, and that (since 3.9) PyObject_CallNoArgs is part of the limited api. |
This looks like a bug to me. While 2ff58a2 added it to the header, it did not add it to https://github.com/python/cpython/blob/master/PC/python3dll.c which is required. |
Yeah, this will be our fault. Someone is looking into automatically generating the .def file so that this stops happening. Last time we tried that there was a lot of pushback because "too many APIs will become stable", but this time I think we're just going to force those devs to care for their APIs properly. (I'm blanking right now on who was working on this... anyone remember?) |
commit fcc6935
I backported the change manually to 3.9: PR 23801. |
Thanks David Hewitt for the bug report, and Zackery Spytz for your fix! 3.9 fix: commit 1662868
|
Note: 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: