Google Git
Sign in
fuchsia / third_party / github.com / python / typing_extensions / 7bb3f3fca39d477b2bb04f64ff5ea2cc14383e51
commit7bb3f3fca39d477b2bb04f64ff5ea2cc14383e51[log] [tgz]
authorAlex Waygood <Alex.Waygood@Gmail.com>Fri Jul 07 15:04:50 2023 +0100
committerGitHub <noreply@github.com>Fri Jul 07 07:04:50 2023 -0700
treee0250e2e956d52492b0a60a5c10cc9df40dafe9a
parent8860c6a143c0a4b3bf6aa0103ca6afee7d0cd5b1 [diff]
Fix third-party workflow (#269)
1 file changed
tree: e0250e2e956d52492b0a60a5c10cc9df40dafe9a
  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.