-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
module is installed, but missing library stubs or py.typed marker #364
Comments
Do you have any information about how that would work in practice / tooling side? Do I need to run something to export the type information on build, or should the build system just do that? |
Well, from a cursory glance at your pyproject.toml it seems that you relies on If you use the current version of setuptools (69.x.x) it should be enough to just create an empty Otherwise, according to pypa/setuptools#3136 it should be necessary to add If you share how you build the packages (what commands do you launch, how are they set up, etc) I may try to do the necessary changes |
I usually just |
added marker file, hopefully that does the trick |
Hi!
|
Could you re-publish the package with the |
Hi.
It seems that, while skimming at the code I see it seems well annotated, the distributed library does not expose it.
From what I know from pep 561 it could be enough to just add an empty
py.typed
in the main package and publish itThe text was updated successfully, but these errors were encountered: