| commit | 19cc3bc38603e284716cfd1047a0679ec3aefc5e | [log] [tgz] |
|---|---|---|
| author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Tue Dec 02 08:44:30 2025 +0100 |
| committer | GitHub <noreply@github.com> | Tue Dec 02 08:44:30 2025 +0100 |
| tree | ab5ace8f26165ec393b2acf3bb8cb1cd96f7b3c0 | |
| parent | 2638b86aad48a3d25704caac9d7e37368fd87815 [diff] |
Update GitHub actions setup-uv and checkout (#703)
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, where x.y is the first version that includes all features you need. This is equivalent to typing_extensions >=x.y, <(x+1). Do not depend on ~= x.y.z unless you really know what you’re doing; that defeats the purpose of semantic versioning.
See the documentation for a complete listing of module contents.
See CONTRIBUTING.md for how to contribute to typing_extensions.