-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Typing PEPs: Link to the typing spec as canonical documentation #3579
Comments
And PR #3575 added the ability to add canonical link banners to the typing spec via intersphinx, like: .. canonical-typing-spec:: :ref:`typing:paramspec` |
I've updated the OP with a checklist. |
Where is the spec for this one? |
PEP 563 was mostly about runtime behavior, not typing behavior. I think it should not be marked final, but Superseded by PEP 649 once that lands (hopefully in 3.13). |
https://docs.python.org/3/library/stdtypes.html#union-type might do pretty well for that one |
688 should point to https://docs.python.org/3/reference/datamodel.html#emulating-buffer-types. 692 should point to https://typing.readthedocs.io/en/latest/spec/callables.html#unpack-for-keyword-arguments |
Almost done! https://peps.python.org/topic/typing/#accepted-peps-accepted-may-not-be-implemented-yet shows: Accepted PEPs (accepted; may not be implemented yet)
|
All done except for PEP 563/649, which is being implemented for 3.14, so we can mark that as final separately when the time comes. Thanks all, let's close this! |
The text of typing PEPs has often served as the canonical reference for how aspects of the type system work. Now that we have the typing spec in place, we should link to it as the canonical documentation, just as we do for packing PEPs that link to packaging.python.org.
(Cross-referencing python/typing#1531, which should make this easier by adding more link targets within the spec.)
TODO:
From https://peps.python.org/topic/typing/#accepted-peps-accepted-may-not-be-implemented-yet:
Later:
The text was updated successfully, but these errors were encountered: