Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when using Git Bash as terminal - Path is wrong formatted #895

Closed
edser-pcg opened this issue Feb 25, 2018 · 2 comments
Closed

Error when using Git Bash as terminal - Path is wrong formatted #895

edser-pcg opened this issue Feb 25, 2018 · 2 comments
Labels
area-terminal bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@edser-pcg
Copy link

edser-pcg commented Feb 25, 2018

Environment data

VS Code version: 1.20.1
Python Extension version: 2018.1.0
Python Version: 3.6.4
OS and version: Windows 10 v1709

Actual behavior

When selecting a Python Linter and having Git Bash defined as your terminal VS Code will try to run the command with a path like: C:\Program Files (x86)\Python36-32\python
This generates an "commando not found" error

Expected behavior

The path should be formatted like C:\\Program Files (x86)\\Python36-32\\python

Steps to reproduce:

  • Configure Git Bash as your Terminal for VS Code
  • Install Python Extension
  • Install Python Code Linter (any)

Logs

Edser@ES-DESK MINGW64 ~/dominican_addons (11.0)
$ C:\Users\Edser\AppData\Local\Programs\Python\Python36-32\python.exe -m pip install -U pylint --user
bash: C:UsersEdserAppDataLocalProgramsPythonPython36-32python.exe: command not found

Edser@ES-DESK MINGW64 ~/dominican_addons (11.0)
$ C:\Users\Edser\AppData\Local\Programs\Python\Python36-32\python.exe -m pip install pylint
bash: C:UsersEdserAppDataLocalProgramsPythonPython36-32python.exe: command not found

Edser@ES-DESK MINGW64 ~/dominican_addons (11.0)
$ C:\\Users\\Edser\\AppData\\Local\\Programs\\Python\\Python36-32\\python.exe -m pip install pylint
Collecting pylint
  Downloading pylint-1.8.2-py2.py3-none-any.whl (689kB)
    100% |████████████████████████████████| 696kB 1.0MB/s
Collecting isort>=4.2.5 (from pylint)
  Downloading isort-4.3.4-py3-none-any.whl (45kB)
    100% |████████████████████████████████| 51kB 2.4MB/s
Collecting six (from pylint)
  Downloading six-1.11.0-py2.py3-none-any.whl
Collecting colorama; sys_platform == "win32" (from pylint)
  Downloading colorama-0.3.9-py2.py3-none-any.whl
Collecting mccabe (from pylint)
  Downloading mccabe-0.6.1-py2.py3-none-any.whl
Collecting astroid<2.0,>=1.6 (from pylint)
  Downloading astroid-1.6.1-py2.py3-none-any.whl (288kB)
    100% |████████████████████████████████| 296kB 2.0MB/s
Collecting lazy-object-proxy (from astroid<2.0,>=1.6->pylint)
  Downloading lazy_object_proxy-1.3.1-cp36-cp36m-win32.whl
Collecting wrapt (from astroid<2.0,>=1.6->pylint)
  Downloading wrapt-1.10.11.tar.gz
Installing collected packages: isort, six, colorama, mccabe, lazy-object-proxy, wrapt, astroid, pylint
  Running setup.py install for wrapt ... done
Successfully installed astroid-1.6.1 colorama-0.3.9 isort-4.3.4 lazy-object-proxy-1.3.1 mccabe-0.6.1 pylint-1.8.2 six-1.11.0 wrapt-1.10.11
@DonJayamanne
Copy link

Please could you try installing the Insiders Build
I believe this has been resolved, and the fix will be in the next release (sometime next week), until then please use the insiders build of the extension above.

@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster area-terminal labels Feb 25, 2018
@DonJayamanne DonJayamanne added this to the February 2018 milestone Feb 25, 2018
@gustavovalverde
Copy link

Tested with Insiders Build, working.

@DonJayamanne DonJayamanne added closed-duplicate and removed info-needed Issue requires more information from poster labels Feb 26, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-terminal bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants