-
Notifications
You must be signed in to change notification settings - Fork 224
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
Windows installation unstable if root path has space (or unicode for Anaconda2) #1029
Comments
I'm not clear from the issue what part is broken. It sounds like Navigator is certainly broken, but I am less certain about the entire install. The mailing list person did seem to say that the anaconda prompt worked, right? |
I guess just to explain a bit: the hard part about saying "we should support spaces" is that every single piece of software in our stack has to conform with that. I still think that we should support it, because it is very common. We had issues with the installer, and I think those are fixed. Now it's something deeper in the stack. Unless there is a test for everything that we install, I think we're doomed to frustrate people. |
I get it. So we could at least tell people the pain they are setting themselves up for if they install into their home directory (which we need to understand might be their only option). |
OK, so this may be a Navigator specific issue for @goanpeca to consider, posted here because it is in discussion in public ML for a non CIO user (whereas the Navigator issue tracker is private). |
Further to the October 1st 2016 Anaconda ML thread for a user with non-ASCII characters in his username, I've updated the title of this issue. |
I dont follow here @ijstokes |
Here is a practical example to help along :
I initially thought it was trying to activate my 2 environments but looking at the root environment activate.bat file that seems to be used when opening a terminal from anaconda, it looks more like a problem of the environment path being interpreted as 2 arguments. While you (hopefully) look into this I'll include my quick fix in case anyone run into the same issue :
|
An additional comment in case helpful : windows provide an alternate name to |
Tracking on #716 |
I am facing this issue also. My user profile has space in it. I don't want to create a new user. Is there no solution for this? |
Spaces in your installation folder should work just fine these days. Can you try the latest releases? |
This is the latest release. I have reinstalled it many times. Same issue, but no problems with other user profiles. C:\Users\Jawad Arshad>conda --version |
I was having similar problems by installing Miniconda in my Users folder (which contains a space). So I did a complete uninstall and reinstalled Miniconda in C:\Miniconda3 (as is suggested here). Here's my output:
|
Hi, I am trying to set up a new anaconda environment, and after locating conda on my command line, I get this error message. How can I get past this?
|
Certain Windows installation configurations use full human names (first SPACE middle SPACE last) appended onto
C:\Users
, e.g.C:\Users\Kevin C Bloom
. If someone installs Anaconda in such a home directory it appears not to work. Spaces in the install path has a long history of creating problems:https://github.com/ContinuumIO/anaconda-issues/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20in%3Atitle%20space
But this is a pretty common one that Anaconda should either support or identify during the install process and warn/abort/prevent the install from proceeding.
The text was updated successfully, but these errors were encountered: