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
Using mypy in code that imports python-tuf does not work yet. We probably need to ship a py.typed file (but this need to be tested: I am not sure how this works)
Existence of py.typed in the top-level package tells users of the
packages that the packages are annotated.
This should fix mypy errors like this in downstream projects:
error: Skipping analyzing "tuf.api.metadata":
found module but no type hints or library stubs
Fixestheupdateframework#1633
Signed-off-by: Jussi Kukkonen <jkukkonen@vmware.com>
Using mypy in code that imports python-tuf does not work yet. We probably need to ship a
py.typed
file (but this need to be tested: I am not sure how this works)https://mypy.readthedocs.io/en/stable/installed_packages.html#creating-pep-561-compatible-packages
The text was updated successfully, but these errors were encountered: