Implement PEP 695

[JelleZijlstra]

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

Linked PRs

• gh-103763: Implement PEP 695 #103764

[preveen-stack]

PEP 695 – Type Parameter Syntax

[sunmy2019]

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]

I feel we should defend the intuitive readability of python irrespective of what.

[JelleZijlstra]

The implementation is done. The next step is #103921, the documentation.

[charliermarsh]

@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?