Run tests on Python 3.13 (#292)

* Run pydantic's tests on py312; bump PyPy to PyPy3.10 for typeguard's tests

Pydantic started testing with py312 in https://github.com/pydantic/pydantic/commit/ea7bf54c2e46d03aedf76b1f661d88971688c7cf

Typeguard bumped the version of PyPy they test with in CI in https://github.com/agronholm/typeguard/commit/9aa873a95d703130894fa28cb511ce04f1b6fd9f

Co-authored-by: Alex Waygood <[email protected]>
4 files changed
tree: 540f10c48b6e0ac4df5d44f5ec81a6f764b5e526
  1. .github/
  2. doc/
  3. src/
  4. .editorconfig
  5. .flake8
  6. .flake8-tests
  7. .gitignore
  8. .readthedocs.yaml
  9. CHANGELOG.md
  10. CONTRIBUTING.md
  11. LICENSE
  12. pyproject.toml
  13. README.md
  14. test-requirements.txt
  15. tox.ini
README.md

Typing Extensions

Chat at https://gitter.im/python/typing

Documentation – PyPI

Overview

The typing_extensions module serves two related purposes:

  • Enable use of new type system features on older Python versions. For example, typing.TypeGuard is new in Python 3.10, but typing_extensions allows users on previous Python versions to use it too.
  • Enable experimentation with new type system PEPs before they are accepted and added to the 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.

Included items

See the documentation for a complete listing of module contents.

Contributing

See CONTRIBUTING.md for how to contribute to typing_extensions.