python
gh-131776: Expose functions called from the interpreter loop via PyAP…
These APIs are used in CPython's interpreter loop. Alternate interpreter loops can be created using the cases_generator script 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.
- Issue: gh-131776
Is it too much to ask for these to be renamed to
PyUnstable?
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 Py_BUILD_CORE to use which means you're already taking a responsibility on if you want to use them. Also there are currently no PyUnstable functions declared at all in the internal header files (even though there are hundreds of exported functions).
Is it too much to ask for these to be renamed to PyUnstable?
PyUnstable functions require documentation and tests.
