Repository navigation
Implement PEP 695 #103763
Description
We should implement PEP-695. Some discussion of the implementation is at https://github.com/erictraut/cpython/issues. I will open a draft PR momentarily.
TODO:
- Evaluate TypeAlias values
- Lazy evaluation for TypeVar bounds
- More tests
- Fix remaining tests in test_typing.py
Activity
preveen-stack commented on Apr 24, 2023
PEP 695 – Type Parameter Syntax
sunmy2019 commented on Apr 24, 2023
Wow. This syntax looks so cool. It reminds me of many generic expressions in other languages, such as C++ and Rust. (while the increases the learning curve of Python)
I'll see what I can help here.
preveen-stack commented on Apr 25, 2023
I feel we should defend the intuitive readability of python irrespective of what.
gh-103763: Implement PEP 695 (#103764)
JelleZijlstra commented on May 16, 2023
The implementation is done. The next step is #103921, the documentation.
Merge branch 'main' into supermon
charliermarsh commented on Jun 22, 2023
@JelleZijlstra - I'm sorry if this is the wrong place to ask, but is the specification and implementation of PEP 695 sufficiently stabilized that I could look into updating Ruff's parser and semantic model to support them?
JelleZijlstra commented on Jun 22, 2023
I don't expect more major changes, no. There are currently no open PEP 695-related bugs; if anything else changes it would be as a result of new feedback we receive during the beta phase.