Why not typeshed?

[hydrargyrum]

The typeshed repository is certainly the right place where to put those types. Why not submitting the project to them?

[sbdchd]

Basically these stubs were started before typeshed releases were disconnected from type checker releases, so by having the types in their own package, it is/was easier to get updates through

[hydrargyrum]

Ok, if this problem is fixed, would you consider submitting it to typeshed? That would also bring much more visibility to your project.

[sbdchd]

Currently these types are pretty incomplete so they would need to be fleshed out more before submission

[jeking3]

It looks like this can be closed? The author is very responsive to bug reports, and I fear within typeshed it may not be as awesome.

[hydrargyrum]

IMHO, I can't see why the project wouldn't be followed if it's in typeshed. Being in typeshed only means it's available to a wider audience and is better integrated in checkers like mypy.

[huyz]

Isn't typeshed deprecated? http://mypy-lang.blogspot.com/2021/05/the-upcoming-switch-to-modular-typeshed.html

[hydrargyrum]

I can't see how it is deprecated. stub_uploader uploads stuff from typeshed repository to separate pypi packages. Your page only mentions reading pypi, which is not incompatible with using the typeshed repository.

[huyz]

Typeshed links to PEP561 which says:

New third party stub libraries SHOULD distribute stubs via the third party packaging methods proposed in this PEP in place of being added to typeshed. Typeshed will remain in use, but if maintainers are found, third party stubs in typeshed MAY be split into their own package.