[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: Jeremy Kloth: > First off, to me, 'unstable' comes off quite negative, i.e. risky or erratic. Ok, the 3rd people who dislike my "unstable" name, so it sounds really bad :-) Jeremy Kloth: > 'volatile'; synonym for 'unstable' but with the benefit of being a C

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

Jeremy Kloth added the comment: As a heavy user of the non-limited Python C API, I would like to offer my suggestions for consideration. (I'm not allowed to post in discourse) First off, to me, 'unstable' comes off quite negative, i.e. risky or erratic. Brett's suggestion of 'broad' is,

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: I created a poll on discuss.python.org for the name of the new subdirectory :-) https://discuss.python.org/t/poll-what-is-your-favorite-name-for-the-new-include-subdirectory/477 -- ___ Python tracker

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: Another proposal: Include\impl\ as in "implementation details". -- ___ Python tracker ___ ___

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: Brett: > The "unstable" name bugs me as it suggests we might change it without notice > which isn't true at all. It's more a limited versus broad API. So maybe > rename the directory "broad"? Brett: Nick proposed "Include\cpython", do you prefer this name?

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

Brett Cannon added the comment: The "unstable" name bugs me as it suggests we might change it without notice which isn't true at all. It's more a limited versus broad API. So maybe rename the directory "broad"? -- nosy: +brett.cannon ___ Python

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: > I think the rules for C includes are that `"path/header.h"` looks next to the > current file first, whereas `` looks only in include > directories. Oh ok, thanks. > However, given your technique of mostly hiding the new directory name from > API

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

Nick Coghlan added the comment: I think the rules for C includes are that `"path/header.h"` looks next to the current file first, whereas `` looks only in include directories. However, given your technique of mostly hiding the new directory name from API consumers, what do you think of

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

STINNER Victor added the comment: Just to avoid the risk of name conflict, would it make sense to rename "unstable" to "pyunstable" or something else with "py" inside? I'm not sure if #include "unstable/objimpl.h" first looks the same directory than the header file that does the include?

[issue35134] Add a new Include/unstable/ subdirectory for the "unstable" API

Change by STINNER Victor : -- title: Move !Py_LIMITED_API to Include/pycapi/ -> Add a new Include/unstable/ subdirectory for the "unstable" API ___ Python tracker ___