A5rocks
Feel free to leave a review for me to fix in a followup PR.
I was concerned for a bit but backwards compaibility is trivial for this. The only times `TrioDeprecationWarning` will happen is for *current* deprecations that should disappear in max 2 releases...
I think current deprecations are fine. They'll be gone in a couple years.
Also re: your mypy bug, my impression was that it just ignores `__new__` in favor of `__init__` if it's available.
Well, `trio==0.23.0` has type hints so I think this issue is done? Reopen if I'm misinterpreting!
I think some people might still want the plugin while mypy doesn't have `TypeVarTuple` ... and I haven't used this much so idk if there's much else here, but maybe...
Looks like people have implemented their own `partial` elsewhere: https://github.com/python/mypy/issues/1484#issuecomment-625423210 But I dunno; might be worth keeping this issue open.
> Can it not be written with something like: > > ```python > async def read_output( > stream: ReceiveStream, > chunks: list[bytes | bytearray], > ) -> None: > async...
Cc @clint-lawrence cause you made the original PR
I think this is ready for review/merge. While this applied as a patch doesn't seem to work, I can't seem to reproduce that and I'm sure it's just some other...