Jelle Zijlstra

Typing PEPs: Link to the typing spec as canonical documentation

8

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](https://typing.readthedocs.io/en/latest/spec/index.html) in place, we...

See python/cpython#98988. PEP 101 should mention that when main switches to a new major version (e.g., 3.11 -> 3.12), `configure` should be updated to add the new version.

https://docs.python.org/3.12/library/dis.html#opcode-POP_TOP (going to send a PR soon to fix this one) The markup here is ``` Removes the top-of-stack item.:: STACK.pop() ``` Perhaps we should detect the sequence `.::` before...

I honestly forgot this slipped into 3.13, but I think it's worth highlighting more, as it is a PEP-sized change that makes the type system significantly more powerful. @Yhg1s I...

gh-117539: Link to the Python typing spec in typing docs

7

This sets up intersphinx and replaces a few PEP links in typing.rst with intersphinx links to the PEPs. I'm going to ask in the Python Docs discord whether there are...

cf. https://discuss.python.org/t/what-are-the-subtyping-rules-for-tuple-t/39837

Improve handling of some string forward references:

1

Discovered that similar errors were treated differently with list[] and List[]. I think we may not need the suppression of undefined names here any more thanks to some other changes.

If `NotRequired` is used with `from __future__ import annotations`, we may not be able to parse the type. Consider always inferring `NotRequired[]` in that case.