But in practice the distinction doesn't seem very conclusive. Some internal APIs end up in either of those two directories without any clear reason why.
Regards Antoine. On Sun, 3 Feb 2019 11:10:16 -0500 Ammar Askar <am...@ammaraskar.com> wrote: > This is the discussion where it was named: > https://discuss.python.org/t/poll-what-is-your-favorite-name-for-the-new-include-subdirectory/477?u=ammaraskar > and the bug explaining the motivation: https://bugs.python.org/issue35134 > > >(and why the additional "pycore_XXX.h" naming convention for some ofthose > >files?) > > "* Include/internal/pycore_*.h is the "internal" API" > > On Sun, Feb 3, 2019 at 10:20 AM Antoine Pitrou <solip...@pitrou.net> wrote: > > > > > > Hello, > > > > Can someone explain why we have two separate directories > > Include/internal and Include/cpython? What is the rule for declaring an > > API inside one or another? > > > > At first sight, it seems to me we're having gratuitous complication > > here. For example, I notice that PyFloat_Fini() is declared in > > Include/cpython/pylifecycle.h but PyLong_Fini() is declared in > > Include/internal/pycore_pylifecycle.h? > > > > (and why the additional "pycore_XXX.h" naming convention for some of > > those files?) > > > > Regards > > > > Antoine. > > > > > > _______________________________________________ > > Python-Dev mailing list > > Python-Dev@python.org > > https://mail.python.org/mailman/listinfo/python-dev > > Unsubscribe: > > https://mail.python.org/mailman/options/python-dev/ammar%40ammaraskar.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
