| commit | 9cb611b865bf4b74114df63b3963fb398302de69 | [log] [tgz] |
|---|---|---|
| author | Alex Waygood <Alex.Waygood@Gmail.com> | Mon Dec 29 22:12:13 2025 +0000 |
| committer | GitHub <noreply@github.com> | Mon Dec 29 23:12:13 2025 +0100 |
| tree | b2d946f85f40dfd2f12cb5549aa8e1f3c35261ef | |
| parent | 19cc3bc38603e284716cfd1047a0679ec3aefc5e [diff] |
Bump shellcheck pin (#713)
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.