Skip to content

Installer fails if there's a space in the path to conda. #12284

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
AnupamSaraph opened this issue Jun 11, 2020 · 5 comments
Closed

Installer fails if there's a space in the path to conda. #12284

AnupamSaraph opened this issue Jun 11, 2020 · 5 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug investigating We are looking into the cause of the issue

Comments

@AnupamSaraph
Copy link

AnupamSaraph commented Jun 11, 2020

Environment data

  • VS Code version:
    Version: 1.45.1 (user setup)
    Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
    Date: 2020-05-14T08:27:35.169Z
    Electron: 7.2.4
    Chrome: 78.0.3904.130
    Node.js: 12.8.1
    V8: 7.8.279.23-electron.0
    OS: Windows_NT x64 10.0.18363

  • Setting python.jediEnabled: false

  • Setting python.languageServer: Microsoft

  • Python and/or Anaconda version: 3.7.6/1.0.1

  • OS: Windows | Mac | Linux (distro): Windows 10

  • Virtual environment: conda

Expected behaviour

Jupyter kernel to start whenever code in a cell is run

Actual behaviour

Visual Studio is declaring that the Datascience libraries jupyter and notebook are missing:
image

Attempt to install locks up with the message:
image

The terminal reports:
image

This is despite the fact that both python and jupyter are installed:

image

Instructions from https://github.com/Microsoft/vscode-python/blob/master/PYTHON_INTERACTIVE_TROUBLESHOOTING.md did not make any difference
did not suggest any remedy that fits the problem

@AnupamSaraph AnupamSaraph added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels Jun 11, 2020
@swebs
Copy link

swebs commented Jun 11, 2020

Looks like a problem handling the space in the user folder name...

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jun 11, 2020
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Jun 11, 2020
@rchiodo rchiodo changed the title Install failure for jupyter Installer fails if there's a space in the path to conda. Jun 11, 2020
@rchiodo rchiodo added the xteam label Jun 11, 2020
@rchiodo
Copy link

rchiodo commented Jun 11, 2020

Looks to me like the space is messing up the run isolated stuff.

@AnupamSaraph
Copy link
Author

Looks to me like the space is messing up the run isolated stuff.

Visual Studio used to work perfectly till about 10 days ago. Did any update change this behaviour?

@AnupamSaraph
Copy link
Author

AnupamSaraph commented Jun 12, 2020

Here's the workaround while the spaces issue paths and file names across windows programs gets resolved:

  • uninstall anaconda and visual studio

  • download from https://www.anaconda.com/products/individual and install anaconda as as administrator for all users (so that it goes to "C:\ProgramData\Anaconda3" that has no spaces

  • download and install visual studio system installer from https://code.visualstudio.com/Download so that it goes into "C:\Program Files\Microsoft VS Code" that visual studio seems to be able to handle

  • run Visual studio, install the python extension and the anaconda extension

Now things work as they did before.

It is evident that some code in visual studio and anaconda is broken if some filenames or paths have spaces. I hope that is fixed soon.

@ericsnowcurrently ericsnowcurrently self-assigned this Jun 15, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jun 15, 2020
@karthiknadig karthiknadig added investigating We are looking into the cause of the issue and removed triage labels Sep 15, 2020
@brettcannon brettcannon removed the xteam label Nov 26, 2020
@karthiknadig
Copy link
Member

As far as I can tell this is fixed. The paths were not quoted properly.
image

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug investigating We are looking into the cause of the issue
Projects
None yet
Development

No branches or pull requests

7 participants