Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-131776: Expose functions called from the interpreter loop via PyAP…#134242
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Is it too much to ask for these to be renamed toPyUnstable?
I'm happy to defer on that, but would be fine renaming them if that seems better. But they're buried in the internal APIs and require defining |
PyUnstable functions require documentation and tests. |
| PyAPI_FUNC(PyObject *) _PyType_LookupSubclasses(PyTypeObject *); | ||
| PyAPI_FUNC(PyObject *) _PyType_InitSubclasses(PyTypeObject *); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
It feels a little off, putting the dict out there to be modified. What do you need this for, specifically? Can we provide some specific operation (like "set a dict watcher") rather than exposing the whole dict?
Uh oh!
There was an error while loading.Please reload this page.
These APIs are used in CPython's interpreter loop. Alternate interpreter loops can be created using the
cases_generatorscript with an additional input file that can be plugged in using PEP 523. But because these functions aren't exposed it's not possible to actually fully create these alternative interpreter loops without copying and pasting large amounts of code.