| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…e as classes NoneType, NotImplementedType and EllipsisType are classes, but were documented with the ".. data::" directive. Unlike the other type objects in the types module they are sometimes referenced as the type of a singleton value, so this is proposed separately from the uncontroversial cases. Switch the three entries to ".. class::", matching the other type objects and the What's New in 3.10 note that introduced them as classes, and update the ":data:" references in constants and the 3.10 What's New page.
Documentation build overview3 files changed ± library/constants.html ± library/types.html ± whatsnew/3.10.html |
Sorry, something went wrong.
|
Please,a void opening automated PRs in a bulk. I'm still not convinced by changing every occurrences mechanically. |
Sorry, something went wrong.
|
Backward-compatibility check. This is the contested subset. The ecosystem still skews class (NoneType 231:27, NotImplementedType 43:2, EllipsisType 113:8 for py:class:py:data), but these carry the most :data: usage in the family, since they are commonly referenced as the type of the None / Ellipsis / NotImplemented singletons. They break more references than the other type-object changes, which is why they are split out for a separate decision. |
Sorry, something went wrong.
|
For those IDK. In some sense with class, I believe autodoc will struggle less. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. 👍
Sorry, something went wrong.
|
Thanks @gaborbernat for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15. |
Sorry, something went wrong.
|
GH-150755 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
|
GH-150756 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
|
GH-150757 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
types.NoneType, types.NotImplementedType, and types.EllipsisType are classes, but the documentation marks them with the .. data:: directive. This part of gh-89554 is worth a separate look: unlike the descriptor and function type objects, these three are sometimes referenced as :data:, as the type of a singleton value such as None.
This proposes switching them to .. class::, matching the other type objects in types.rst and the What's New in 3.10 entry that introduced them, which already describes them as "classes". It also updates the :data: references in Doc/library/constants.rst and Doc/whatsnew/3.10.rst to :class:.
I am happy to drop this if you would rather keep .. data:: for the singleton-value types. It is split out from the uncontroversial cases in #150676 so the decision can be made on its own.
Refs: gh-89554. Documentation-only change, so no Misc/NEWS entry (skip news).
cc @AA-Turner as the Lib/types.py maintainer.