Third-party stubs are generally removed from typeshed when one of the following criteria is met:
The upstream package ships a py.typed file for at least six months, or
[...]
We've had a few cases recently, where upstream added a py.typed file, but the annotations were clearly sub-par compared to the stubs from typeshed. In an ideal world, we'd contribute back our annotations, but that usually requires quite a bit of effort – even compared with continuing to support the stubs in typeshed. (Even if improving upstream's annotations and removal from typeshed should of course be the ultimate goal.)
I suggest to amend our policy to say:
The upstream package ships a py.typed file for at least six months, and the upstream type annotations are of a comparable standard to those in typeshed, [...]
The wording still leaves some wiggle room, and isn't overly specific, but is more specific than "usually" for this case.
Currently our policy says:
We've had a few cases recently, where upstream added a
py.typed
file, but the annotations were clearly sub-par compared to the stubs from typeshed. In an ideal world, we'd contribute back our annotations, but that usually requires quite a bit of effort – even compared with continuing to support the stubs in typeshed. (Even if improving upstream's annotations and removal from typeshed should of course be the ultimate goal.)I suggest to amend our policy to say:
The wording still leaves some wiggle room, and isn't overly specific, but is more specific than "usually" for this case.