commit | e90eb68913e3e3cb501b57db33a1bc19f125b075 | [log] [tgz] |
---|---|---|
author | Charlie Boutier <[email protected]> | Tue Jul 09 17:46:47 2024 +0000 |
committer | Automerger Merge Worker <[email protected]> | Tue Jul 09 17:46:47 2024 +0000 |
tree | b71d7a0d4dd0dc63bd7297e24dce3eb0b43b21f5 | |
parent | 33b5122b50f25c96d3bb82e8566449a32f6cfadf [diff] | |
parent | bb82318427e3a95144732d7eebb2baa5c8264fcc [diff] |
typing_extensions: use newest version am: bb82318427 Original change: https://android-review.googlesource.com/c/platform/external/python/typing_extensions/+/3162322 Change-Id: Ie40056bfea614442460ce0763ba0f222572a2ffd Signed-off-by: Automerger Merge Worker <[email protected]>
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
.