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
So, section "Storing and distributing stub files" in PEP 484 gives a way to distribute *.pyi. But how to package a project such that it's in-code type annotations are taken in consideration by mypy? Currently, I'm just installing the *.py directly, which keep the type annotations.
Setting MYPYPATH to /usr/lib/python3.4/site-packages will make it fail, so I guess there should be a fallback if a module is not found, to look for it directly in the site-packages. Or is there a flag I missed?
The text was updated successfully, but these errors were encountered:
So, section "Storing and distributing stub files" in PEP 484 gives a way to distribute
*.pyi
. But how to package a project such that it's in-code type annotations are taken in consideration by mypy? Currently, I'm just installing the*.py
directly, which keep the type annotations.Setting MYPYPATH to
/usr/lib/python3.4/site-packages
will make it fail, so I guess there should be a fallback if a module is not found, to look for it directly in thesite-packages
. Or is there a flag I missed?The text was updated successfully, but these errors were encountered: