-
Notifications
You must be signed in to change notification settings - Fork 44
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
The package is typed but there is no py.typed file #47
Comments
Hey and thanks for the hint. I actually didn't know about the |
I think so |
A
So, as long as this project is a single-module project, no |
Thanks for the response! Up to you whether to keep the issue open or not.
…On Wed, Apr 27, 2022, 17:20 Ingo Meyer ***@***.***> wrote:
A py.typed marker is added in commit
be7b3a9. *However*, this won't work at
the moment. 😞 PEP561 mentions:
This PEP does not support distributing typing information as part of
module-only distributions or single-file modules within namespace packages.
The single-file module should be refactored into a package and indicate
that the package supports typing as described above.
So, as long as this project is a single-module project, no py.typed
marker will be installed and thus, MyPy won't detect the typing support. I
plan to restructure the project anyway to support Windows, so I can merge
this change later...
—
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACYQXXKAI3GISDFUWJL4FLLVHFEJBANCNFSM5UOBMPAA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You went through the trouble of typing your package - adding a py.typed file to it will help type analysis.
The text was updated successfully, but these errors were encountered: