-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Consider adding a py.typed file to the package #2
Comments
I spoke a bit too soon. It seems that in |
Hi @peteris-zealid, Sorry, took me a while to get to this one. I added |
Hi, I thought this was a closed issue, but thank you for letting me know. Sometimes it pains my heart to see you not getting paid for all the quality work (and support) you are doing on this lib. |
Well, my GitHub Sponsors registration request finally got processed yesterday, so there's an avenue now... ;) Not that I have grand expectations about the revenue that would generate, though :) |
Hello,
I ran
mypy
on the codebase and it revealed only a few minor issues. Nothing that the end user would ever care about. On one hand it might be slightly irresponsible to add a py.typed marker without setting up a type checker to run at each commit, but on the other hand automatically generated stubs will be of much lower quality and should be avoided for practical purposes.The text was updated successfully, but these errors were encountered: