PEP 695 type parameters are not colored correctly

[debonte]

Awesome to have syntax highlighting for PEP 695 type aliases. However, type parameter are still missing unfortunately.

from typing import Generic, TypeVar

T = TypeVar("T")

class X(Generic[T]):
    def __init__(self, var: T) -> None: ...


class Y[T]:
    def __init__(self, var: T) -> None: ...

Originally posted by Marc Mueller (@cdce8p) in #5541

[Avasam]

It's even worse on function-scoped generics since the arrow becomes red

Relates to

• switch to a different tool for python syntax highlighting #5824
• Support for PEP 695 (Type parameters / generics) MagicStack/MagicPython#262
• add rudimentary support for PEP 695 MagicStack/MagicPython#270

[heejaechang]

Rechecked this in the current prerelease on a fresh VS Code session using the generated repro workspace, with editor.semanticHighlighting.enabled still set to false.

The behavior from the original report is no longer reproducing:

• the T tokens in class Y[T] and def foo[T](...) -> T are colored distinctly again, consistent with the older generic syntax path
• the -> arrow no longer falls back to the error-like/plain-text styling from the original screenshot

Given that fresh rerun result, I’m closing this as no longer reproducible in current builds.