You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think lazy evaluation of type statements is something we can do while also keeping type checkers happy, so probably we'll just stick with the existing string-based solution (though since we'll use the literal syntax on 3.12, we'll still get the lazy evaluation there).
Actually, we need to also emit literal syntax for def f[T](...): ... as well, since if we don't it messes up typing.overload declarations by inserting the typevar declarations in-between.
Activity
[-]Fully support [PEP 695](https://peps.python.org/pep-0695/)[/-][+]Fully support PEP 695[/+]evhub commentedon May 28, 2023
I don't think lazy evaluation of
typestatements is something we can do while also keeping type checkers happy, so probably we'll just stick with the existing string-based solution (though since we'll use the literal syntax on 3.12, we'll still get the lazy evaluation there).evhub commentedon May 29, 2023
Tuple constraint syntax should work now, but I'll probably wait until 3.12 is released to get all the literal syntax working.
Add type param constraint support
evhub commentedon Feb 25, 2024
This is basically done except that it can't really be tested yet because
mypystill doesn't support it.evhub commentedon Mar 21, 2024
Actually, we need to also emit literal syntax for
def f[T](...): ...as well, since if we don't it messes uptyping.overloaddeclarations by inserting the typevar declarations in-between.Improve PEP 695 implementation
evhub commentedon Apr 15, 2024
I think the only thing remaining now is we're just waiting on
mypyto support this so we can test it on 3.12.Release v3.1.1 (#842)
evhub commentedon Sep 1, 2024
We're waiting for
infer_variancesupport here: python/mypy#15238evhub commentedon Oct 23, 2024
It looks like this has now been moved to here: python/mypy#17811