| commit | 2638b86aad48a3d25704caac9d7e37368fd87815 | [log] [tgz] |
|---|---|---|
| author | Semyon Moroz <donbarbos@proton.me> | Tue Nov 18 23:45:35 2025 +0400 |
| committer | GitHub <noreply@github.com> | Tue Nov 18 19:45:35 2025 +0000 |
| tree | 0ad58b37e0c3388cbb33ec3ee17beecee38edea8 | |
| parent | f684c9a36b8490985bf285404810a65ef6fdfc78 [diff] |
Remove `no_type_check_decorator` from `__all__` for Python >= 3.15 (#699)
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.