A5rocks
Looks like this approach doesn't handle type vars (I think that's what you're seeing): ```py import dataclasses from typing import Protocol, TypeVar, ParamSpec, Generic, Callable T = TypeVar("T", covariant=True) P...
Here's something closer to my platonic ideal: ``` + Exception Group Traceback (most recent call last): | File "/home/h/Git/trio/clean_tb/test_foo.py", line 16, in | trio.run(main) | ~~~~~~~~^^^^^^ | File "/home/h/Git/trio/clean_tb/src/trio/_core/_run.py", line...
Actually part of this is just https://github.com/python-trio/trio/issues/2649 I think
Well I missed that you actually approved it! I'll respond to your review.
Nevermind, I was thinking about whether a deprecation is possible but it isn't because the problem is functions having ki protection only sometimes.
"type preciseness" is just tracking Anys, correct? I'm pretty sure we handle those explicitly with type ignore comments, having enabled plenty of Any-related errors. I guess it can't hurt though....
I'm still not sure of the utility of this. The only use case I can think of is someone on a machine which can't run mypy trying to find a...
Yeah I was thinking of the job summary thing, but actually that only supports markdown :/ Maybe we could publish these results from main to some GitHub Pages thing (I...
OK I don't know why RTD is failing to clone this PR now...
Well it seems to work now. I'll merge this soon enough unless someone has comments.