Skip to content
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

C API: mention the workgroup, and the need to be stricter than our public promises #1524

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

encukou
Copy link
Member

@encukou encukou commented Feb 28, 2025

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/

@encukou encukou requested review from vstinner and zooba February 28, 2025 14:09
@encukou encukou marked this pull request as draft February 28, 2025 14:24
Co-authored-by: Hugo van Kemenade <[email protected]>
@encukou encukou marked this pull request as ready for review February 28, 2025 15:03
@erlend-aasland erlend-aasland self-requested a review March 2, 2025 11:40
(:ref:`python:api-intro`).

Internally, we need to be more careful about compatibility than what we promise
publicly. See :ref:`public-capi` for details.
Copy link
Member

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?

Copy link
Member

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"?

Comment on lines +27 to +28
Internally, we need to be more careful about compatibility than what we promise
publicly. See :ref:`public-capi` for details.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this work?

Suggested change
Internally, we need to be more careful about compatibility than what we promise
publicly. See :ref:`public-capi` for details.
As core developers, we need to be more careful about compatibility than what
we promise publicly. See :ref:`public-capi` for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants