python / typing Public

Co-authored-by: Erik De Bonte <erikd@microsoft.com>

As promised in https://bugs.python.org/issue46386

Backported:
- python/cpython#30619

Not backported:
- python/cpython#30613 (because `ParamSpec` is already tested with `pickle` using all protocols)

…1018)

typing exists in all supported Python versions

…ersion (#1024)

As pointed out in #1023, there is no risk of incompatibility, since the
requires-python field will prevent installation on older Python versions.

* Test on Python 3.11 pre-releases

* Update linter config

Per the Python docs and PEPs, `TypeAlias` appears to have been defined in PEP 613, not PEP 610.

Co-authored-by: Shantanu <12621235+hauntsaninja@users.noreply.github.com>

* Add section headers to the toc tree
* Add a "Guides" section and put the libraries document there
* Move the link to the typing documentation into the "Reference" section

Cf. #845

Prior to this, the toctree directives pointed at numerous planned but
unpopulated docs. The result is a mostly empty site with the real
content buried.

To revert without discarding work, the toctrees which list empty files
are commented out, and new tables of contents are added to link to
`libraries` and `stubs` (the existing, populated sections).

Stub docs are left in place, producing sphinx warnings about unlinked
docs. These are expected.

The link to the typing module docs has been restored, now in a
dedicated section.

Came up in python/typeshed#6619

Adds a local copy of _SpecialForm in our namespace, so
typing._type_check won't raise TypeError. (#964)

Co-authored-by: James Hilton-Balfe <50501825+Gobot1234@users.noreply.github.com>

The previous link sent the user to the German version of the site

- Add an explicit inclusion policy: new stuff can go in here as soon as there is a PEP
- Remove obsolete discussion of the typing PyPI package
- Organize the list of contents by Python version, so it's easier to find the interesting bits. Maybe we should deprecate the stuff that was new in 3.5/3.6 at some point.