| commit | 04f98954ba63a5e8a09c12171be24785298276b6 | [log] [tgz] |
|---|---|---|
| author | Miro Hrončok <miro@hroncok.cz> | Wed Oct 18 20:26:19 2023 +0200 |
| committer | GitHub <noreply@github.com> | Wed Oct 18 11:26:19 2023 -0700 |
| tree | 182daad6fbf09a5ab45914c00ee58194741f062a | |
| parent | b6318ab4b4777a38b468eef7aae97061c283eb8d [diff] |
Fix tests on Python 3.13 (#291) This is a followup for d95cc228ea96feec105592a9902e5b2d6cc048a9 The removed block raises TypeError on Python 3.13+. The TypeError is already asserted in test_keywords_syntax_raises_on_3_13. For older Pythons, the DeprecationWarning and __name__ + __annotations__ value are already asserted in test_typeddict_special_keyword_names.
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.