You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this intentional, or just an oversight? I think the py.typed mechanism is there because some people use annotations internally, but their annotations perhaps aren't accurate enough for their library's users to rely on. So they don't want to "publish" them, even though they're right there in the shipped code. Omitting the py.typed file means that the annotations aren't usable.
The text was updated successfully, but these errors were encountered:
Hi, yes types are not ready to be public. There is a bunch of what we need to fix and enable more strict checks. That for now is disabled. In the future type checking must be a part of CI on every PR
Thanks for explaining the current status. It might be that the types for the parts I use are good enough, and then if mypy fixes python/mypy#8545 I'll be sorted :-)
Everything has type annotations, but there's no
py.typed
files in the top-level packages to tell mypy that it should use them: https://peps.python.org/pep-0561/#packaging-type-informationIs this intentional, or just an oversight? I think the py.typed mechanism is there because some people use annotations internally, but their annotations perhaps aren't accurate enough for their library's users to rely on. So they don't want to "publish" them, even though they're right there in the shipped code. Omitting the py.typed file means that the annotations aren't usable.
The text was updated successfully, but these errors were encountered: