Many users not aware that Python modules are not automatically resolved

[karrtikr]

Many users are not aware that they need to explicitly create a .env file, with PYTHONPATH variable set to the relative location where modules need to be searched. This is generally interpreted as a bug.

The usual complaint is "I can run these python files fine but vscode is throwing warnings/errors"

Have to come up with a solution to resolve such python modules in vscode out of the box.

[jakebailey]

For reference, the LS has a new doc section that covers adding multiple roots via extraPaths: https://github.com/microsoft/python-language-server/blob/master/TROUBLESHOOTING.md#unresolved-import-warnings

But automatically generating this configuration or suggesting something would be a good idea if possible.

[luabud]

Closing in favour of #924