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
This issue is occurring with Debian GNU/Linux 9.8 (stretch), Python 3.7.2, and mypy 0.680+dev.3cea8326d5fbc67030316ccc4addc4297af6daaa. Here is a script to reproduce it:
mypy finds the package when MYPYPATH is given as an environment variable but not when mypy_path is given in mypy.ini. As best I can tell, here's what happens:
This issue is occurring with Debian GNU/Linux
9.8 (stretch)
, Python3.7.2
, and mypy0.680+dev.3cea8326d5fbc67030316ccc4addc4297af6daaa
. Here is a script to reproduce it:Output (after the installation):
mypy
finds the package whenMYPYPATH
is given as an environment variable but not whenmypy_path
is given inmypy.ini
. As best I can tell, here's what happens:main.main
callsmain.process_options
main.process_options
callsmain.process_config_file
--package
argument has been given,main.process_options
callsmodulefinder.mypy_path
modulefinder.mypy_path
gets the path fromMYPYPATH
andmain.process_options
never usesoptions.mypy_path
I can remedy the problem with the following change:
If this is not expected behavior and this change is all that's needed, I am happy to make a pull request.
The text was updated successfully, but these errors were encountered: