commit | d6c50f585c386490d38ad6b8ce5543aed6e633a2 | [log] [tgz] |
---|---|---|
author | Jelle Zijlstra <jelle.zijlstra@gmail.com> | Wed Feb 14 08:52:43 2024 -0800 |
committer | GitHub <noreply@github.com> | Wed Feb 14 17:52:43 2024 +0100 |
tree | 67b07f9593df28e7e8c33e644071c89d9457c6f2 | |
parent | ff530f50e2e1440e870dfecd2f59a5ae9d2a4244 [diff] |
Drop runtime error in PEP 705 implementation (#333) See https://discuss.python.org/t/pep-705-read-only-typeddict-items/37867/10
The typing_extensions
module serves two related purposes:
typing.TypeGuard
is new in Python 3.10, but typing_extensions
allows users on previous Python versions to use it too.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.
See the documentation for a complete listing of module contents.
See CONTRIBUTING.md for how to contribute to typing_extensions
.