-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
Make PyCode_GetFirstFree a PEP-689 unstable API #115756
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
|
The name should be |
Shouldn't this apply to |
The function is part of Python 3.12 release, and after Python 3.12, you want to downgrade the API to the unstable API in Python 3.13? It sounds too late for me, no? |
I'll leave that for the C API WG ;) |
Downgrading means that the public name, |
I don't think that it's worth it. If later, the function becomes stable, depending on the Python version, PyCode_GetFirstFree() may be deprecated or not, it sounds unpleasant for a minor issue. Honestly, just elaborate the documentation to express more clearly the stability contract, no? |
I don't think the intention is to ever make it stable. It exposes an implementation detail: free variables follow other ones in a code object.
This is the way to do that. |
Ping @markshannon |
Thank you! |
Originally posted by @markshannon in #115654 (comment)
Linked PRs
The text was updated successfully, but these errors were encountered: