Closed
Description
Currently whenever mypy fails to find an import it prints a note suggesting to set MYPYPATH, e.g.:
main:1: error: Cannot find module named 'a.b.c'
main:1: note: (Perhaps setting MYPYPATH or using the "--ignore-missing-imports" flag would help)
In most cases setting MYPYPATH is an anti-pattern, since the issue is likely that this is a third-party module for which no stubs exist in typeshed (nor anywhere else). We used to see a lot of problems when people added site-packages to MYPYPATH.
Maybe we can add a more nuanced explanation to the docs and link to the docs from the note instead?