Add docs for --namespace-packages #5749
Conversation
| Note that this only affects import discovery -- for modules and | ||
| packages explicitly passed on the command line, mypy still | ||
| searches for ``__init__.py[i]`` files in order to determine the | ||
| fully-qualified module/package name. |
There was a problem hiding this comment.
Maybe it would be worth talking about what to do in order to explicitly check code in namespace packages?
There was a problem hiding this comment.
What about things like mypy -m foo.bar if foo is a namespace package? Users may expect it to work, since the module name is explicit. Similarly, what about mypy -p foo if foo is a namespace package?
There was a problem hiding this comment.
Hm, none of those currently work. Maybe they should, but I don't have time to make it work in this release (command line files/modules/packages use an entirely different code path than imported modules). I'll open a new issue.
There was a problem hiding this comment.
mypy -c 'import foo.bar', I suppose?
There was a problem hiding this comment.
Hm, there are still problems with that. I'm not sure why. Will try to look into this before the release goes out.
It might surprise people. Plus PEP 420 only applies to Python 3. If there's demand (and the bugs are shaken out) we can enable it by default for Python 3 in the future. |
Follow-up for #5691. Should be cherry-picked into the release (#5741). Fixes #5757.