You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
assignee=Noneclosed_at=<Date2020-12-16.21:43:38.059>created_at=<Date2020-11-19.22:47:45.721>labels= ['3.9', '3.10', 'extension-modules', 'expert-C-API', 'build', 'OS-windows']
title='python3.lib in Python3.9.0 Windows distribution does not contain PyObject_CallNoArgs symbol'updated_at=<Date2020-12-16.21:43:38.058>user='https://bugs.python.org/DavidHewitt'
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.
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?)
Add symbols of the stable ABI to python3dll.c (GH-23598) (GH-23801)
Add the following symbols to python3dll.c:
* PyFrame_GetCode (bpo-40421)
* PyFrame_GetLineNumber (bpo-40421)
* PyObject_CallNoArgs (bpo-37194)
* PyThreadState_GetFrame (bpo-39947)
* PyThreadState_GetID (bpo-39947)
* PyThreadState_GetInterpreter (bpo-39947)
(cherry picked from commit fcc6935384b933fbe1a1ef659ed455a3b74c849a)