-
-
Notifications
You must be signed in to change notification settings - Fork 850
C API: mention the workgroup, and the need to be stricter than our public promises #1524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Hugo van Kemenade <[email protected]>
developer-workflow/c-api.rst
Outdated
(:ref:`python:api-intro`). | ||
|
||
Internally, we need to be more careful about compatibility than what we promise | ||
publicly. See :ref:`public-capi` for details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand this paragraph. What do you mean by "internally"? The internal C API?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps "Within the core development group" is a better phrase than "internally"?
(Sorry for leaving the messy default commit message, I misclicked.) |
Draft for now: this refers to an addition to
python:api-intro
that I'm proposing in python/cpython#130686📚 Documentation preview 📚: https://cpython-devguide--1524.org.readthedocs.build/