Google Git
Sign in
fuchsia / third_party / github.com / python / typing_extensions / refs/heads/main
commit99fa708df2af1ab5ecde47968d71dc5b0447fc5d[log] [tgz]
authorAlex Waygood <Alex.Waygood@Gmail.com>Thu Aug 03 17:07:10 2023 +0100
committerGitHub <noreply@github.com>Thu Aug 03 09:07:10 2023 -0700
treeea33f113b2d1d239cc58be7d35a3554c7df24620
parent688fbd2545944c9c36a0d08084e7c92642a81751 [diff]
Backport CPython PR 107584 (#275)
3 files changed
tree: ea33f113b2d1d239cc58be7d35a3554c7df24620
  1. .github/
  2. doc/
  3. src/
  4. .editorconfig
  5. .flake8
  6. .flake8-tests
  7. .gitignore
  8. CHANGELOG.md
  9. CONTRIBUTING.md
  10. LICENSE
  11. pyproject.toml
  12. README.md
  13. test-requirements.txt
  14. 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.