Autocomplete fails with paths listed in PYTHONPATH via .env file

[xgalaxy]

Environment data

VS Code version:
Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:23:26.125Z)

Python Extension version:
0.8.0

Python Version:
Python 2.7.14 :: Anaconda, Inc.

OS and version:
Darwin x64 16.7.0

Actual behavior

Auto complete does not work properly with additional packages listed in PYTHONPATH added via the .env file.

Expected behavior

Auto complete will list documentation, methods, functions, etc. from packages listed in PYTHONPATH.

Steps to reproduce:

• Add paths to PYTHONPATH via the workspace .env file
• Notice that pylint seems to pick up the extra paths just fine. But auto complete fails to work.

[DonJayamanne]

Please could you provide a sample (sample repo).
Also, have you tried reloading VS Code (currently you'll need to reload vscode after editingthe .env file)

[xgalaxy]

Here is an example repo: https://github.com/xgalaxy/python_test

I created a .env file that exposes the libs folder modules to PYTHONPATH. While this exposes the libs path to the linters correctly, the autocompletion and cmd+click navigation and documentation for the modules in libs doesn't function unless you also add the libs path to python.autocomplete.extraPaths.

In my opinion I think the extra paths and .env system needs an overhaul. I shouldn't have to list the same paths in multiple places to get a complete functioning development environment.

I would remove the .env file completely and rename python.autocomplete.extraPaths to python.extraPaths and expose the paths in that setting to every python tool; the linters, autocompletion system, documentation system, debugger, etc.

[DonJayamanne]

Thanks for the sample repo.

In my opinion I think the extra paths and .env system needs an overhaul. I shouldn't have to list the same paths in multiple places to get a complete functioning development environment.

Agreed, this will be resolved with the issue #228.

Just confirming, this issue would get resolved along with #228. All you'll need to do is add the settings in .env. file (and you wouldn't need to reload vscode).

[brettcannon]

I'm closing this as it has been over a month since we requested more info. If we do get the info at a later date we can re-open this issue.

[xgalaxy]

Not sure what more info you needed. An example repo was requested and provided.

[brettcannon]

@xgalaxy if you look at the last message from @DonJayamanne he asked you to test something out to verify if something would fix your issue.

[xgalaxy]

No, adding those paths to env won't work. As is stated in the original ticket comments and the very title of this ticket. Am I misunderstanding something here?

[brettcannon]

We have released a new version of the extension since you first reported this so we wanted you to validate for us whether the issue persisted for you as we think we fixed it.