GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||
GeezerVison is showing github.com — gh-106320: Remove private _Py_Identifier API by vstinner · Pull Request #108593 · python/cpython Conversation
|
|
Related discussion: https://discuss.python.org/t/c-api-how-much-private-is-the-private-py-identifier-api/29190 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
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.
d593732 to
7ccbf0b
Compare
|
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.
There was an error while loading. Please reload this page.
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.
There was an error while loading. Please reload this page.
I created #111484 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.