Google Git
Sign in
fuchsia / third_party / github.com / python / typing_extensions / refs/heads/upstream/JelleZijlstra-patch-1
commitb3a96af95524656efa79edf958fb2cec08e938fc[log] [tgz]
authorJelle Zijlstra <jelle.zijlstra@gmail.com>Sun Mar 10 20:46:35 2024 -0700
committerGitHub <noreply@github.com>Sun Mar 10 20:46:35 2024 -0700
tree6b6309a8e6dbda1b59e8c6e76429e43fd41343c4
parentd409ec98e3889462e59c85a4b34f9f83ce40bf2c [diff]
Test that CI runs
1 file changed
tree: 6b6309a8e6dbda1b59e8c6e76429e43fd41343c4
  1. .github/
  2. doc/
  3. src/
  4. .editorconfig
  5. .flake8
  6. .flake8-tests
  7. .gitignore
  8. .readthedocs.yaml
  9. CHANGELOG.md
  10. CONTRIBUTING.md
  11. LICENSE
  12. pyproject.toml
  13. README.md
  14. test-requirements.txt
  15. tox.ini
README.md

Typing Extensions

Chat at https://gitter.im/python/typing

Documentation – PyPI

Overview

The typing_extensions module serves two related purposes:

  • Enable use of new type system features on older Python versions. For example, typing.TypeGuard is new in Python 3.10, but typing_extensions allows users on previous Python versions to use it too.
  • Enable experimentation with new type system PEPs before they are accepted and added to the typing module.

typing_extensions is treated specially by static type checkers such as mypy and pyright. Objects defined in typing_extensions are treated the same way as equivalent forms in typing.

typing_extensions uses Semantic Versioning. The major version will be incremented only for backwards-incompatible changes. Therefore, it's safe to depend on typing_extensions like this: typing_extensions >=x.y, <(x+1), where x.y is the first version that includes all features you need.

Included items

See the documentation for a complete listing of module contents.

Contributing

See CONTRIBUTING.md for how to contribute to typing_extensions.