We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I propose adding a banner to all C API documentation pages to recommend using 3rd party tools, rather than using directly the C API.
See the discussion on HPy: https://discuss.python.org/t/c-api-working-group-and-plan-to-get-a-python-c-api-compatible-with-alternative-python-implementations/89477/41
The text was updated successfully, but these errors were encountered:
pythongh-133678: Add a banner to C API doc to recommend tools
5d7ad68
-1. I think CPython should have a usable and stable C API for all stakeholders, and a list of a few blessed users goes against that goal.
Extend the current list with the ideas here, but please don't add a new one and don't link to it aggressively from every page.
Sorry, something went wrong.
-1. I think CPython should have a usable and stable C API for all stakeholders,
The banner doesn't change anything to the C API maintenance. It will remain the same.
and a list of a few blessed users goes against that goal.
Do you mean that the list is too short? Or do you mean that developers should be able/"allowed" to write C extensions directly with the C API?
Why do you think that it's aggressive? Can you propose a different phrasing to make it not aggressive?
What's the motivation for this change, then?
Both.
Why do you think that it's aggressive?
It's on every page of the reference.
No branches or pull requests
I propose adding a banner to all C API documentation pages to recommend using 3rd party tools, rather than using directly the C API.
See the discussion on HPy: https://discuss.python.org/t/c-api-working-group-and-plan-to-get-a-python-c-api-compatible-with-alternative-python-implementations/89477/41
Linked PRs
The text was updated successfully, but these errors were encountered: