-
-
Couldn't load subscription status.
- Fork 33.3k
gh-135755: Document __future__.* and CO_* as proper Sphinx objects #135980
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
This'll make it easier to add entries that need longer markup
|
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
…cts (pythonGH-135980) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros. (cherry picked from commit 2468aaf) Co-authored-by: Petr Viktorin <[email protected]>
|
Sorry, @encukou, I could not cleanly backport this to |
|
GH-136370 is a backport of this pull request to the 3.14 branch. |
|
GH-136371 is a backport of this pull request to the 3.13 branch. |
…nx objects (pythonGH-135980) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros. (cherry picked from commit 2468aaf) Co-authored-by: Petr Viktorin <[email protected]>
…ects (GH-135980) (GH-136370) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros. (cherry picked from commit 2468aaf) Co-authored-by: Petr Viktorin <[email protected]>
…cts (pythonGH-135980) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros.
…cts (pythonGH-135980) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros.
…cts (pythonGH-135980) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros.
…ects (GH-135980) (GH-136371) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros. (cherry picked from commit 2468aaf) Co-authored-by: Petr Viktorin <[email protected]>
…cts (pythonGH-135980) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros.
…cts (pythonGH-135980) * Turn the __future__ table to list-table. This'll make it easier to add entries that need longer markup * Semantic markup for __future__ feature descriptions. * Document CO_* C macros.
__future__feature descriptions andCO_C macros were documented in prose, but lacked Sphinx markup that marked them as Python attributes and C macros. For example:inspect.CO_GENERATOR(Python data, in inspect — Inspect live objects)”, but no C API.This affects users of the Intersphinx inventory as well.
This patch adds the Sphinx definintions, and puts them in
list-tables to make the ReST more maintainabile.📚 Documentation preview 📚: https://cpython-previews--135980.org.readthedocs.build/