Extension version (available under the Extensions sidebar): XXX
OS and version: Windows 7 SP1
Python version (& distribution if applicable, e.g. Anaconda): 2.7.14
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Expected behaviour
To run python projects using the current Python in the local environment.
No issues with previous version.
Actual behaviour
Tries to run the python with location:
"C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\python.exe"
Had to amend the python.pythonPath setting to:
"C:\Python27\python.exe" for it to continue to work.
Shouldn't this take from the current local environment "PATH" settings?
Steps to reproduce:
Launch python script with default "python" as python path with multiple installations of python on machine, Including Visual Studio Python and standard C:\python27 installation.
Logs
E:\Projects\synths>cd E:\Projects\synths && cmd /C "set "PYTHONPATH=C:\Python27\DLLs;C:\Python27\Lib\lib-tk;E:\Projects;E:\Projects\synths;" && set "PYTHONIOENCODING=UTF-8" && set "PYTHONUNBUFFERED=1" && "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\python.exe" c:\Users\james.morrell\.vscode\extensions\ms-python.python-2019.1.0\pythonFiles\ptvsd_launcher.py --default --client --host localhost --port 58007 E:\***************.py "
Traceback (most recent call last):
File "c:\Users\james.morrell\.vscode\extensions\ms-python.python-2019.1.0\pythonFiles\ptvsd_launcher.py", line 21, in <module>
import ptvsd
File "c:\Users\james.morrell\.vscode\extensions\ms-python.python-2019.1.0\pythonFiles\lib\python\ptvsd\__init__.py", line 13, in <module>
from ._vendored import force_pydevd
File "c:\Users\james.morrell\.vscode\extensions\ms-python.python-2019.1.0\pythonFiles\lib\python\ptvsd\_vendored\force_pydevd.py", line 20, in <module>
pydevd_constants = import_module('_pydevd_bundle.pydevd_constants')
File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\lib\importlib\__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "c:\Users\james.morrell\.vscode\extensions\ms-python.python-2019.1.0\pythonFiles\lib\python\ptvsd\_vendored\pydevd\_pydevd_bundle\pydevd_constants.py", line 164, in <module>
from _pydev_imps._pydev_saved_modules import thread
File "c:\Users\james.morrell\.vscode\extensions\ms-python.python-2019.1.0\pythonFiles\lib\python\ptvsd\_vendored\pydevd\_pydev_imps\_pydev_saved_modules.py", line 8, in <module>
import socket
File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\lib\socket.py", line 49, in <module>
import _socket
ImportError: DLL load failed: %1 is not a valid Win32 application.
Internal error detected. Please copy the above traceback and report at
https://github.com/Microsoft/vscode-python/issues/new
Press Enter to close. . .
No (this change was introduced last release).
You need to specify what is to be used. Else it will use the best available interpreter (i.e. latest python version available on your system).
Environment data
Expected behaviour
To run python projects using the current Python in the local environment. No issues with previous version.
Actual behaviour
Tries to run the python with location: "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python36_64\python.exe"
Had to amend the python.pythonPath setting to: "C:\Python27\python.exe" for it to continue to work.
Shouldn't this take from the current local environment "PATH" settings?
Steps to reproduce:
Logs
Current Environment PATH: