-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
C API: Rename _PyUnstable_GetUnaryIntrinsicName() to PyUnstable_GetUnaryIntrinsicName()? #107149
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
Move PyUnstable_ExecutableKinds and associated macros from the internal C API to the public C API.
Move PyUnstable_ExecutableKinds and associated macros from the internal C API to the public C API.
* Rename _PyUnstable_GetUnaryIntrinsicName() to PyUnstable_GetUnaryIntrinsicName() * Rename _PyUnstable_GetBinaryIntrinsicName() to PyUnstable_GetBinaryIntrinsicName().
I doubt there was a reason for the _. Probably just a habit. |
* Rename _PyUnstable_GetUnaryIntrinsicName() to PyUnstable_GetUnaryIntrinsicName() * Rename _PyUnstable_GetBinaryIntrinsicName() to PyUnstable_GetBinaryIntrinsicName().
Move PyUnstable_ExecutableKinds and associated macros from the internal C API to the public C API.
…inds Rename contants, replace Py with _Py (add underscore prefix): * PY_EXECUTABLE_KIND_SKIP = > _PY_EXECUTABLE_KIND_SKIP * PY_EXECUTABLE_KIND_PY_FUNCTION => _PY_EXECUTABLE_KIND_PY_FUNCTION * PY_EXECUTABLE_KIND_BUILTIN_FUNCTION => _PY_EXECUTABLE_KIND_BUILTIN_FUNCTION * PY_EXECUTABLE_KIND_METHOD_DESCRIPTOR => _PY_EXECUTABLE_KIND_METHOD_DESCRIPTOR * PY_EXECUTABLE_KINDS => _PY_EXECUTABLE_KINDS
…inds Rename contants, replace Py with _Py (add underscore prefix): * PY_EXECUTABLE_KIND_SKIP = > _PY_EXECUTABLE_KIND_SKIP * PY_EXECUTABLE_KIND_PY_FUNCTION => _PY_EXECUTABLE_KIND_PY_FUNCTION * PY_EXECUTABLE_KIND_BUILTIN_FUNCTION => _PY_EXECUTABLE_KIND_BUILTIN_FUNCTION * PY_EXECUTABLE_KIND_METHOD_DESCRIPTOR => _PY_EXECUTABLE_KIND_METHOD_DESCRIPTOR * PY_EXECUTABLE_KINDS => _PY_EXECUTABLE_KINDS
Move PyUnstable_ExecutableKinds and associated macros from the internal C API to the public C API. Rename constants: replace "PY_" prefix with "PyUnstable_" prefix.
Move PyUnstable_ExecutableKinds and associated macros from the internal C API to the public C API. Rename constants: replace "PY_" prefix with "PyUnstable_" prefix.
At the end, all APIs discussed here are public and exposed with the |
Unstable API needs documentation and tests. |
Perhaps #105481 (which added the APIs in question) should be reopened instead. |
It's not easy to see on that issue what you mean (which unstable APIs? That issue contained several large PRs that change many things). I think it actually works better to finish it off on this issue or create a new one than to report a large old issue. |
Also, PyUnstable_ExecutableKinds was not added in #105481. |
Reopening. See #105481 (comment). |
Change implemented by 36aab34. I close again the issue. |
…ublic and unstable (python#112042)
…ublic and unstable (python#112042)
Python 3.13 added
_PyUnstable_GetUnaryIntrinsicName()
and_PyUnstable_GetBinaryIntrinsicName()
to the C API. I don't get the_PyUnstable
prefix: PEP 689 – Unstable C API tier usesPyUnstable_
prefix.Is it just a typo, or is the API private on purpose? If it's private, why does its name look like as if it's part of the Unstable C API?
cc @brandtbucher @iritkatriel @encukou
Linked PRs
The text was updated successfully, but these errors were encountered: