[issue43416] Add README files in Include/cpython and Include/internal

Change by STINNER Victor : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue43416] Add README files in Include/cpython and Include/internal

STINNER Victor added the comment: New changeset 929c9039fe0468cb37e0811ddfb7b67c98353ea8 by Erlend Egeberg Aasland in branch 'master': bpo-43416: Add Include/README.rst (GH-24884) https://github.com/python/cpython/commit/929c9039fe0468cb37e0811ddfb7b67c98353ea8 --

[issue43416] Add README files in Include/cpython and Include/internal

Change by Erlend Egeberg Aasland : -- keywords: +patch nosy: +erlendaasland nosy_count: 3.0 -> 4.0 pull_requests: +23643 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24884 ___ Python tracker

[issue43416] Add README files in Include/cpython and Include/internal

STINNER Victor added the comment: * Include/internal/ with extern: C API which must not and can not be used outside CPython code base, only stdlib extensions built as built-in extensions can use it. * Include/internal/ with PyAPI_FUNC/PyAPI_DATA: API which should be be used outside

[issue43416] Add README files in Include/cpython and Include/internal

New submission from Serhiy Storchaka : I always hesitate in what subdirectory of Include/ to add a declaration of new private API. What is more "private"? It would be nice to add README files in these directories which describe what API should be declared here and what is the difference