Skip to content

pyvsc-run-isolated slashes not escaped in Git Bash on Windows #13005

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

Closed
kimadeline opened this issue Jul 16, 2020 · 5 comments
Closed

pyvsc-run-isolated slashes not escaped in Git Bash on Windows #13005

kimadeline opened this issue Jul 16, 2020 · 5 comments
Labels
area-terminal bug Issue identified by VS Code Team member as probable bug regression Bug didn't exist in a previous release

Comments

@kimadeline
Copy link

System info:

  • Windows 10
  • VS Code version: 1.47.1
  • Extension version: 2020.6.91350
  • Git Bash

Steps:

  • Create a virtual environment, don't install anything and set it as your interpreter path
  • Enable linting in the repo, and install pylint when prompted

image

Text on the screenshot:

Kim@DESKTOP-BINGO MINGW64 ~/Documents/Work/vscode-python/pythonFiles (main)
$ source c:/Users/Kim/Documents/Work/vscode-python/.venv/Scripts/activate
(.venv) 
Kim@DESKTOP-BINGO MINGW64 ~/Documents/Work/vscode-python/pythonFiles (main)
$ c:/Users/Kim/Documents/Work/vscode-python/.venv/Scripts/python.exe c:\Users\K
im\.vscode\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isola
ted.py pip install -U pylint
C:\Python38\python.exe: can't open file 'c:UsersKim.vscodeextensionsms-python.python-2020.6.91350pythonFilespyvsc-run-isolated.py': [Errno 2] No such file or directory
(.venv) 
Kim@DESKTOP-BINGO MINGW64 ~/Documents/Work/vscode-python/pythonFiles (main)
$ 

Related: #734 #700 and mayyyybe #11419

@kimadeline kimadeline added bug Issue identified by VS Code Team member as probable bug triage-needed Needs assignment to the proper sub-team labels Jul 16, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jul 20, 2020
@karthiknadig karthiknadig added area-terminal regression Bug didn't exist in a previous release labels Jul 20, 2020
@brbecker
Copy link

brbecker commented Aug 9, 2020

Same issue on:

  • Windows 10
  • VS Code version: 1.47.3
  • Extension version: 2020.7.96456
  • Git Bash 2.28.0

@bengartner
Copy link

Same issue on:

  • Windows 10
  • VS Code 1.48.1
  • Extension: ms-python.python-2020.8.105045
  • Git bash: git version 2.27.0.windows.1

@Coronon
Copy link

Coronon commented Sep 18, 2020

For me it even deleted many of the 'pythonFiles' in the Python extension, I had to completely reinstall the extension to fix the bug. This happened to me after having multiple venvs in my project.

Env:

  • Windows 10
  • VS Code 1.49.0
  • Extension: ms-python.python-2020.8.109390
  • Shell: Windows Powershell

I can not even select my default interpreter now

Quick fix:

  1. Remove extension in VSCode
  2. Close all VSCode instances
  3. Delete extension foldern folder in ?/.vscode/extensions called ms-python.python-{version}
  4. Open VSCode again and install Python extension

@testworksau
Copy link

In order to get this working, in Terminal -> terminal dropdown -> Select Default Shell, choose anything except Git Bash or WSL Bash.

Interestingly, the escaping in WSL bash looks better but doesn't take the /mnt/ path into account.

image

@karrtikr
Copy link

Closing as we removed pyvsc-run-isolated.py file.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2021
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 regression Bug didn't exist in a previous release
Projects
None yet
Development

No branches or pull requests

7 participants