Sebastian Rittau
Sebastian Rittau
@danieleades I'm sorry for the late answer. I would just ignore the pyright warnings using `# pyright: ignore`. Alternatively you could just mark those methods using `@staticmethod` in the stubs...
I've merged @donBarbos's PR. This now has (as expected) merge conflicts.
Unfortunately, there are now a few stubtest errors, possibly due a new yt-dlp release in the meantime: https://github.com/python/typeshed/actions/runs/16541009423/job/46782207654?pr=14216
typeshed-internal/stub_uploader#177 will fix the stub uploader problem.
I still tend towards (2), although easy protocol composition would go a long way here. `Reader` and `Writer` were originally intended to be broader to encompass most cases, but became...
Also, overload "merging" behavior plays into this a little. E.g. given the example above and assuming that only the first and last overload were specified, could `foo` be called with...
Thanks, this seems to be a remnant from PEP 646 (https://peps.python.org/pep-0646/#unpacking-unbounded-tuple-types) where `Tuple[int, ...]` as used in the section as an example.
I'm also not sure why this doesn't work. Still I think for now it's best to postpone (i.e. close) this PR, until this works better.
If in doubt, always assume that the stubs are wrong first. :) PR welcome!
We always squash merge. For future reference: Please don't force push during development, that makes reviewing harder.