| commit | 53e41c5aacb67855a9ccffb7d2b6cbaa3c600f90 | [log] [tgz] |
|---|---|---|
| author | Inna Palant <[email protected]> | Mon Jul 08 19:54:59 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Mon Jul 08 19:54:59 2024 +0000 |
| tree | e02861217e581b502a751387f3aeef4919b23beb | |
| parent | de8f10b8ecebf0d872889cfafd451fc348f7d139 [diff] | |
| parent | 33b5122b50f25c96d3bb82e8566449a32f6cfadf [diff] |
Merge remote-tracking branch 'origin/upstream' am: aedd517eda am: 33b5122b50 Original change: undetermined Change-Id: I74f8cda9dea18659e3550bd4cff3c0956079a808 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.