gh-106320: Remove private _Py_Identifier API#108593
Conversation
Sorry, something went wrong.
|
Related discussion: https://discuss.python.org/t/c-api-how-much-private-is-the-private-py-identifier-api/29190 |
Sorry, something went wrong.
Remove the private _Py_Identifier type and related private functions from the public C API: * _PyObject_GetAttrId() * _PyObject_LookupSpecialId() * _PyObject_SetAttrId() * _PyType_LookupId() * _Py_IDENTIFIER() * _Py_static_string() * _Py_static_string_init() Move them to the internal C API: add a new pycore_identifier.h header file. No longer export these functions.
vstinner
force-pushed
the
pycore_identifier
branch
from
d593732 to
7ccbf0b
Compare
August 29, 2023 00:00
|
Is there a recommendation for what to use instead? I read the discussion linked, but it didn't seem like there was a conclusion on the replacement. |
Sorry, something went wrong.
I'm worried about these APIs :-( No consensus was found on a migration plan to move away from this private API. Maybe we should consider adding back the private API for now until a clear consensus is found. |
Sorry, something went wrong.
I created #111484 |
Sorry, something went wrong.
3 participants
Remove the private _Py_Identifier type and related private functions from the public C API:
Move them to the internal C API: add a new pycore_identifier.h header file. No longer export these functions.