Setting module search path in the config file

[JukkaL]

I wonder if we should support configuring the module search path (equivalent to MYPYPATH) in the mypy config file. I have a feeling that this was discussed before, but maybe we can revisit this.

Here's one particular use case I'm thinking about: specifying a directory for custom stubs. For example, I could have a stubs/ subdirectory in my repository for custom stubs that I've written. It seems reasonable to be able to add this directory to the search path automatically so I won't always have to use a script that sets MYPYPATH for running mypy correctly. If I use --silent-imports, a mypy run with accidentally missing search path items will pass without errors and can easily generate false negatives.

[ffigiel]

Yes, please. There's too much work with submitting stubs for 3rd party libraries to typeshed.

I managed to side-step this problem by adding ./stubs to MYPYPATH. That said, the config file would be a much more convenient place for this setting.

Here's my use case:

• I run stubgen foo
• Remove everything except for the things I use from the stub
• Commit the stub

[gvanrossum]

Yes, we should do this.

@megapctr Do you feel up to submitting a PR for this? If not we can try to do it.

[ffigiel]

I'm on it 👍

[ddfisher]

I agree that we want this, but for working on typeshed --custom-typeshed-dir (which should be ready for merge in #1588) should be a bit more convenient.

[gvanrossum]

Closed by #2329.