Google Git
Sign in
fuchsia / third_party / github.com / python / typing_extensions / refs/tags/4.9.0
commitfc461d6faf4585849b561f2e4cbb06e9db095307[log] [tgz]
authorJelle Zijlstra <jelle.zijlstra@gmail.com>Sat Dec 09 17:11:53 2023 -0800
committerGitHub <noreply@github.com>Sat Dec 09 17:11:53 2023 -0800
tree3cf831ce53729499d45e259fb17ea7902424e7c5
parentf82d6367f3ff8f16b6291de06394ec6b9318bfc3 [diff]
Release 4.9.0 (#313)
2 files changed
tree: 3cf831ce53729499d45e259fb17ea7902424e7c5
  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.