commit | ece1201226c557f7328638e065b4a6c5ec4e13ce | [log] [tgz] |
---|---|---|
author | Alex Waygood <Alex.Waygood@Gmail.com> | Sat Jun 15 16:20:56 2024 +0100 |
committer | GitHub <noreply@github.com> | Sat Jun 15 08:20:56 2024 -0700 |
tree | ad090af48fac467f25fa055fa66a15e26f55af98 | |
parent | 2d33f1f51df3f9f1601aae9a068e36937f78e966 [diff] |
Backport bugfixes made to how `inspect.get_annotations()` deals with PEP-695 (#428)
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
.