Need help in installing anaconda
I tried installing anaconda for my AI project using python. When I try to install anaconda on to my new laptop but when the prompt comes to where I should be saving my file I get this warning "Destination folder contains 1 space. This can cause problems with several conda packages. Please consider removing the space."
I am trying to save the file on my C drive but I keep getting this warning and my laptop is also new. How do solve this issue. Please help
2 Answers 2
It might be because your username has space in it like C:\Jon Doe\Anaconda3\
Install anaconda at C:\Anaconda3\ or something
Destination folder contains 1 space anaconda что это
При установке программы Anaconda возникает следующее предупреждение:
Warning: ‘Destination Folder’ contains 1 space. This can cause problems with several Conda packages. Please consider removing the space.
Жмем Ок и вылетает ошибка
Error: Due to incompatibility with several Python libraries, I Destination Folder’ cannot contain non-ascii characters (special characters or diacritics). Please choose another location.
Жмем опять Ок и остаемся в том же окне.
Для устранения ошибки следует поменять путь.
Создать на диске C папку с именем программы и указать путь в окне Choose Install Location к данной папке. Ошибка должна исчезнуть.
Насколько публикация полезна?
Нажмите на звезду, чтобы оценить!
Средняя оценка 4.5 / 5. Количество оценок: 19
Anaconda Navigator not initializing. #1659
Comments
agrawalmanisha commented May 4, 2017
After completing the installation process I am trying to launch Anaconda Navigator but its throwing the following error: «Python has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.»
I have uninstalled and reinstalled the package few times. But the problem persists.
The text was updated successfully, but these errors were encountered:
mingwandroid commented May 4, 2017
Please install to a location without spaces and try again.
agrawalmanisha commented May 4, 2017
how do I do that? I am new to Python and don’t understand spaces.
mingwandroid commented May 4, 2017 •
Spaces are nothing to do with Python. Spaces are the thing between words in written (natural) languages, sometimes it’s called whitespace but I don’t like that term: https://en.wikipedia.org/wiki/Whitespace_character
In the dialog that says «Choose Install Location», in the box that says «Destination Folder» please enter something that doesn’t contain any space characters. An example of a «Destination Folder» that contains 2 space characters would be: «C:\Users\Ray Donnelly\Programming Stuff\Anaconda3» and an example of a «Destination Folder» that doesn’t would be: «C:\Anaconda3».
agrawalmanisha commented May 4, 2017
i have reinstalled Anaconda3 at a different location on my system. Still I am not being able to initialize Anaconda Navigator. Its throwing the following error: «Python has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.»
mingwandroid commented May 4, 2017
Can you try to launch the Anaconda Prompt instead, then from there type:
anaconda-navigator
.. and report what happens?
agrawalmanisha commented May 4, 2017
agrawalmanisha commented May 4, 2017
i have found the problem. I have downloaded Anaconda3 at the following location: C:\Python. But when I am running Anaconda Navigator, its stored at the following location by default:
C:\Users\M A N I S H A\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Anaconda3 (64-bit)
Thus these spaces are creating the problem. Please advice how to deal with the same.
I am not being able to change the name M A N I S H A or remove the spaces from here. So please advice.
mingwandroid commented May 4, 2017
Spaces in the ‘Start Menu’ location are not the problem here. Please do this:
Can you try to launch the Anaconda Prompt (from the ‘Start Menu’) instead, then from there type:
anaconda-navigator
.. and report what happens?
agrawalmanisha commented May 4, 2017
It started Initializing then the same error message: «Python has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.»
mingwandroid commented May 4, 2017 •
agrawalmanisha commented May 4, 2017
(C:\Python) C:\Users\M A N I S H A>anaconda-navigator
(C:\Python) C:\Users\M A N I S H A>echo %PATH%
C:\Python;C:\Python\Library\mingw-w64\bin;C:\Python\Library\usr\bin;C:\Python\Library\bin;C:\Python\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\MiKTeX 2.9\miktex\bin\x64;C:\Program Files (x86)\Skype\Phone;C:\Program Files\Git\cmd;C:\Python;C:\Python\Scripts;C:\Python\Library\bin;C:\Users\M A N I S H A\AppData\Local\Programs\Python\Python36\Scripts;C:\Users\M A N I S H A\AppData\Local\Programs\Python\Python36;C:\Users\M A N I S H A\AppData\Local\Microsoft\WindowsApps;
(C:\Python) C:\Users\M A N I S H A>conda info
Current conda install:
packages in environment at C:\Python:
_license 1.1 py36_1 defaults
alabaster 0.7.9 py36_0 defaults
anaconda 4.3.1 np111py36_0 defaults
anaconda-client 1.6.0 py36_0 defaults
anaconda-navigator 1.5.0 py36_0 defaults
anaconda-project 0.4.1 py36_0 defaults
astroid 1.4.9 py36_0 defaults
astropy 1.3 np111py36_0 defaults
babel 2.3.4 py36_0 defaults
backports 1.0 py36_0 defaults
beautifulsoup4 4.5.3 py36_0 defaults
bitarray 0.8.1 py36_1 defaults
blaze 0.10.1 py36_0 defaults
bokeh 0.12.4 py36_0 defaults
boto 2.45.0 py36_0 defaults
bottleneck 1.2.0 np111py36_0 defaults
bzip2 1.0.6 vc14_3 [vc14] defaults
cffi 1.9.1 py36_0 defaults
chardet 2.3.0 py36_0 defaults
chest 0.2.3 py36_0 defaults
click 6.7 py36_0 defaults
cloudpickle 0.2.2 py36_0 defaults
clyent 1.2.2 py36_0 defaults
colorama 0.3.7 py36_0 defaults
comtypes 1.1.2 py36_0 defaults
conda 4.3.14 py36_1 defaults
conda-env 2.6.0 0 defaults
configobj 5.0.6 py36_0 defaults
console_shortcut 0.1.1 py36_1 defaults
contextlib2 0.5.4 py36_0 defaults
cryptography 1.7.1 py36_0 defaults
curl 7.52.1 vc14_0 [vc14] defaults
cycler 0.10.0 py36_0 defaults
cython 0.25.2 py36_0 defaults
cytoolz 0.8.2 py36_0 defaults
dask 0.13.0 py36_0 defaults
datashape 0.5.4 py36_0 defaults
decorator 4.0.11 py36_0 defaults
dill 0.2.5 py36_0 defaults
docutils 0.13.1 py36_0 defaults
entrypoints 0.2.2 py36_0 defaults
et_xmlfile 1.0.1 py36_0 defaults
fastcache 1.0.2 py36_1 defaults
flask 0.12 py36_0 defaults
flask-cors 3.0.2 py36_0 defaults
freetype 2.5.5 vc14_2 [vc14] defaults
get_terminal_size 1.0.0 py36_0 defaults
gevent 1.2.1 py36_0 defaults
greenlet 0.4.11 py36_0 defaults
h5py 2.6.0 np111py36_2 defaults
hdf5 1.8.15.1 vc14_4 [vc14] defaults
heapdict 1.0.0 py36_1 defaults
icu 57.1 vc14_0 [vc14] defaults
idna 2.2 py36_0 defaults
imagesize 0.7.1 py36_0 defaults
ipykernel 4.5.2 py36_0 defaults
ipython 5.1.0 py36_0 defaults
ipython_genutils 0.1.0 py36_0 defaults
ipywidgets 5.2.2 py36_1 defaults
isort 4.2.5 py36_0 defaults
itsdangerous 0.24 py36_0 defaults
jdcal 1.3 py36_0 defaults
jedi 0.9.0 py36_1 defaults
jinja2 2.9.4 py36_0 defaults
jpeg 9b vc14_0 [vc14] defaults
jsonschema 2.5.1 py36_0 defaults
jupyter 1.0.0 py36_3 defaults
jupyter_client 4.4.0 py36_0 defaults
jupyter_console 5.0.0 py36_0 defaults
jupyter_core 4.2.1 py36_0 defaults
lazy-object-proxy 1.2.2 py36_0 defaults
libpng 1.6.27 vc14_0 [vc14] defaults
libtiff 4.0.6 vc14_3 [vc14] defaults
llvmlite 0.15.0 py36_0 defaults
locket 0.2.0 py36_1 defaults
lxml 3.7.2 py36_0 defaults
markupsafe 0.23 py36_2 defaults
matplotlib 2.0.0 np111py36_0 defaults
menuinst 1.4.4 py36_0 defaults
mistune 0.7.3 py36_0 defaults
mkl 2017.0.1 0 defaults
mkl-service 1.1.2 py36_3 defaults
mpmath 0.19 py36_1 defaults
multipledispatch 0.4.9 py36_0 defaults
nbconvert 4.2.0 py36_0 defaults
nbformat 4.2.0 py36_0 defaults
networkx 1.11 py36_0 defaults
nltk 3.2.2 py36_0 defaults
nose 1.3.7 py36_1 defaults
notebook 4.3.1 py36_2 defaults
numba 0.30.1 np111py36_0 defaults
numexpr 2.6.1 np111py36_2 defaults
numpy 1.11.3 py36_0 defaults
numpydoc 0.6.0 py36_0 defaults
odo 0.5.0 py36_1 defaults
openpyxl 2.4.1 py36_0 defaults
openssl 1.0.2k vc14_0 [vc14] defaults
pandas 0.19.2 np111py36_1 defaults
partd 0.3.7 py36_0 defaults
path.py 10.0 py36_0 defaults
pathlib2 2.2.0 py36_0 defaults
patsy 0.4.1 py36_0 defaults
pep8 1.7.0 py36_0 defaults
pickleshare 0.7.4 py36_0 defaults
pillow 4.0.0 py36_0 defaults
pip 9.0.1 py36_1 defaults
ply 3.9 py36_0 defaults
prompt_toolkit 1.0.9 py36_0 defaults
psutil 5.0.1 py36_0 defaults
py 1.4.32 py36_0 defaults
pyasn1 0.1.9 py36_0 defaults
pycosat 0.6.1 py36_1 defaults
pycparser 2.17 py36_0 defaults
pycrypto 2.6.1 py36_5 defaults
pycurl 7.43.0 py36_2 defaults
pyflakes 1.5.0 py36_0 defaults
pygments 2.1.3 py36_0 defaults
pylint 1.6.4 py36_1 defaults
pyopenssl 16.2.0 py36_0 defaults
pyparsing 2.1.4 py36_0 defaults
pyqt 5.6.0 py36_2 defaults
pytables 3.2.2 np111py36_4 defaults
pytest 3.0.5 py36_0 defaults
python 3.6.0 0 defaults
python-dateutil 2.6.0 py36_0 defaults
pytz 2016.10 py36_0 defaults
pywin32 220 py36_2 defaults
pyyaml 3.12 py36_0 defaults
pyzmq 16.0.2 py36_0 defaults
qt 5.6.2 vc14_3 [vc14] defaults
qtawesome 0.4.3 py36_0 defaults
qtconsole 4.2.1 py36_2 defaults
qtpy 1.2.1 py36_0 defaults
requests 2.12.4 py36_0 defaults
rope 0.9.4 py36_1 defaults
ruamel_yaml 0.11.14 py36_1 defaults
scikit-image 0.12.3 np111py36_1 defaults
scikit-learn 0.18.1 np111py36_1 defaults
scipy 0.18.1 np111py36_1 defaults
seaborn 0.7.1 py36_0 defaults
setuptools 27.2.0 py36_1 defaults
simplegeneric 0.8.1 py36_1 defaults
singledispatch 3.4.0.3 py36_0 defaults
sip 4.18 py36_0 defaults
six 1.10.0 py36_0 defaults
snowballstemmer 1.2.1 py36_0 defaults
sockjs-tornado 1.0.3 py36_0 defaults
sphinx 1.5.1 py36_0 defaults
spyder 3.1.2 py36_0 defaults
sqlalchemy 1.1.5 py36_0 defaults
statsmodels 0.6.1 np111py36_1 defaults
sympy 1.0 py36_0 defaults
tk 8.5.18 vc14_0 [vc14] defaults
toolz 0.8.2 py36_0 defaults
tornado 4.4.2 py36_0 defaults
traitlets 4.3.1 py36_0 defaults
unicodecsv 0.14.1 py36_0 defaults
vs2015_runtime 14.0.25123 0 defaults
wcwidth 0.1.7 py36_0 defaults
werkzeug 0.11.15 py36_0 defaults
wheel 0.29.0 py36_0 defaults
widgetsnbextension 1.2.6 py36_0 defaults
win_unicode_console 0.5 py36_0 defaults
wrapt 1.10.8 py36_0 defaults
xlrd 1.0.0 py36_0 defaults
xlsxwriter 0.9.6 py36_0 defaults
xlwings 0.10.2 py36_0 defaults
xlwt 1.2.0 py36_0 defaults
zlib 1.2.8 vc14_3 [vc14] defaults
(C:\Python) C:\Users\M A N I S H A>where Q5tCore.dll
INFO: Could not find files for the given pattern(s).
QMake has two modes, one mode for generating project files based on
some heuristics, and the other for generating makefiles. Normally you
shouldn’t need to specify a mode, as makefile generation is the default
mode for qmake, but you may use this to test qmake on an existing project
Support spaces in the install path for the installers #716
Comments
csoja commented Mar 21, 2016 •
There are cases on UNIX where a user wants to be able install Anaconda on a path that has spaces. (@maysonicboom) (Currently the installer does not support this and gives the user the correct warning message.)
The text was updated successfully, but these errors were encountered:
goanpeca commented May 17, 2017
Lets use this issue @mingwandroid as a placeholder for any issue related to spaces
uctptep commented Oct 7, 2017 •
I just experienced this issue with Anaconda3 5.0.0 and Python 3 on Windows 10 as described in #1029
rsokl commented Feb 21, 2018 •
What is the status of this issue? One of my students just hit this issue on Windows.
mingwandroid commented Feb 21, 2018
Should be fixed, but really, try not to use paths with spaces if you can avoid it.
rsokl commented Feb 21, 2018
The default directory structure and anaconda-installation location on Windows has space in it for the average user. I know not to do this myself, but it is hard to deftly instruct some
200 high school students in an online course towards this end.
Was there ever a PR that resolved this?
chrisconlan commented Feb 26, 2018
I just tried ignoring the alert about spaces in usernames and following through with the installation. After working for a few hours, Anaconda Prompt ended up losing track of my virtual environments.
Using thinks like C:\Users\CHRISC
1\Anaconda3 as an installation path doesn’t work. Installer treats
as an illegal character.
Installing as root uses C:\ProgramData\Anaconda3 by default on Windows 10, which solves the issue of spaces in the path. If this continues to work as a temporary solution, I am fine with it.
stevengj commented Nov 5, 2018 •
It looks like the required changes to the Unix installer.sh are fairly minor. Basically, you just need to tell it to use the bash getopts built-in rather than the getopt command (which doesn’t handle spaces), add a few missing » marks, and disable some code that checked for spaces in the prefix.
Here is a minimal hack to illustrate this, which works on my machine. (I just disabled the byte-count check here.)
I agree that other command-line tools may have bugs for paths with spaces, but I don’t think the installer should refuse to install. Give a warning at most.
stevengj commented Nov 5, 2018
(If I wanted to submit a PR for this, where would I submit to? I’m not sure which repo the miniconda installer is in.)
mingwandroid commented Nov 5, 2018 •
From my current perspective (the amount of collatoral damage this would cause), I’m not sure fixing this is in anyone’s best interests.
Are you aware that we do text based prefix replacement in things like bash scripts when necessary? PATHs and env vars?, so a file may contain:
and we replace that with:
.. what happens when we inspect GDAL_ROOT?
Then you have the issue of Unix tools that we provide that were written with the explicit assumption that spaces would not be supported in file paths. What happens when someone tries to build a conda package using GNU make (one of these tools)? Support requests?
mingwandroid commented Nov 5, 2018 •
BTW, on Windows, this issue is far less of an issue since Windows software is coded (or the WIndows specific parts are coded) so that spaces in paths work and often so that trivial relocation works. Unforutunately much of the Unix world is oriented towards installing to a known fixed prefix (often space-incompatible) and we are left to deal with that as best we can.
chrisconlan commented Nov 5, 2018
My original complaint was Windows-based. Definitely still an issue.
The trick with Windows is to select “install as root” so that you minimize the chance of spaces in the path.
mingwandroid commented Nov 5, 2018
If you do want to submit a PR the URL is here: https://github.com/conda/constructor
mingwandroid commented Nov 5, 2018
@chrisconlan you didn’t provide any reproducible steps for your problem, it’s far too nebulous for us to look into as things stand. You say it’s definitely still an issue, at what version of Miniconda or Anaconda does that statement stand?
FWIW I don’t believe we have a big problem on Windows around spaces, based on my own testing.
If you can provide a simple reproduction case we can try to look into it. You say ‘virtualenv’ specifically though, do you mean conda environments here?
mingwandroid commented Nov 5, 2018
@chrisconlan if you want to continue this it would be best to open a new issue here and fill in the template details.
chrisconlan commented Nov 5, 2018 •
I wanted to raise the issue but I don’t have time to gut my Windows machine.
Feel free to ignore me if you don’t think it’s an issue anymore.
mingwandroid commented Nov 5, 2018
Oh I’m not ignoring you, we just have our priorities.
chrisconlan commented Nov 5, 2018
mingwandroid commented Nov 5, 2018
Can you answer about the nature of the envs. you had trouble with? Knowing which software (conda, virtualenv, venv, pipenv) caused you trouble is fundamental to being able to fix it;
chrisconlan commented Nov 5, 2018
If I remember correctly, I had just factory reset a windows machine, and I was trying to install Anaconda again.
I opted to install on a user level and not global/root level, which caused Anaconda to install on C:\Users\Chris Conlan\Anaconda3. I got the warning about spaces, but proceeded anyway.
I only used conda environments, not venv or virtualenv, and then I started to notice my conda environments would persist for one session then disappear the next. This was through the Anaconda Promot only, and through activate.bat.
I uninstalled and reinstalled Anaconda as global/root on Windows to C:\ProgramData\Anaconda3 and had no problems.
That’s the best I got. Hope it helps.
mingwandroid commented Nov 5, 2018
Yes, that’s helpful, thanks.
nilavra commented May 30, 2019
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).
This new installation should not have anything to do with my User directory, as it is (should be?) completely detached. Yet somehow whenever I try to activate an environment, I get similar errors like this.
JawadAr commented Jun 8, 2019 •
Is there still no solution to this? I am tired of updating my conda packages every now and then to see if the issue is fixed. Can this be fixed? How can I help?
It is simple to understand the problem. Bear with me please, I got a brand new laptop, DELL G3 15 with windows 10 preinstalled. I installed chrome and downloaded the LATEST anaconda installer. I opened anaconda prompt not power shell not cmd. I created an environment and activated it. It all worked nice and good, then I restarted my machine (unfortunately) and opened the anaconda prompt but this error was showing:
My user profile has a space in it and now I cannot activate any environment. I don’t want to make a new user nor do I want to reinstall my windows. I did reinstall anaconda on root but still this issue persists.
Opening the anaconda prompt as an admin gives this error:
@chrisconlan you didn’t provide any reproducible steps for your problem, it’s far too nebulous for us to look into as things stand. You say it’s definitely still an issue, at what version of Miniconda or Anaconda does that statement stand?
FWIW I don’t believe we have a big problem on Windows around spaces, based on my own testing.
If you can provide a simple reproduction case we can try to look into it. You say ‘virtualenv’ specifically though, do you mean conda environments here?
@mingwandroid Hope it is not too nebulous now.
JawadAr commented Jun 8, 2019
The output of «conda init»:
I find it hard to use the information given in the links you have provided. But I did make sure that I have removed everything and installed the anaconda clean again. I face similar problems with the windows cmd.
kousu commented Apr 29, 2021 •
pkgs/main/linux-64::conda-package-handling-1.7.2-py38h03888b9_0 cryptography pkgs/main/linux-64::cryptography-3.2.1-py38h3c74f83_1 idna pkgs/main/noarch::idna-2.10-py_0 ld_impl_linux-64 pkgs/main/linux-64::ld_impl_linux-64-2.33.1-h53a641e_7 libedit pkgs/main/linux-64::libedit-3.1.20191231-h14c3975_1 libffi pkgs/main/linux-64::libffi-3.3-he6710b0_2 libgcc-ng pkgs/main/linux-64::libgcc-ng-9.1.0-hdf63c60_0 libstdcxx-ng pkgs/main/linux-64::libstdcxx-ng-9.1.0-hdf63c60_0 ncurses pkgs/main/linux-64::ncurses-6.2-he6710b0_1 openssl pkgs/main/linux-64::openssl-1.1.1h-h7b6447c_0 pip pkgs/main/linux-64::pip-20.2.4-py38h06a4308_0 pycosat pkgs/main/linux-64::pycosat-0.6.3-py38h7b6447c_1 pycparser pkgs/main/noarch::pycparser-2.20-py_2 pyopenssl pkgs/main/noarch::pyopenssl-19.1.0-pyhd3eb1b0_1 pysocks pkgs/main/linux-64::pysocks-1.7.1-py38h06a4308_0 python pkgs/main/linux-64::python-3.8.5-h7579374_1 readline pkgs/main/linux-64::readline-8.0-h7b6447c_0 requests pkgs/main/noarch::requests-2.24.0-py_0 ruamel_yaml pkgs/main/linux-64::ruamel_yaml-0.15.87-py38h7b6447c_1 setuptools pkgs/main/linux-64::setuptools-50.3.1-py38h06a4308_1 six pkgs/main/linux-64::six-1.15.0-py38h06a4308_0 sqlite pkgs/main/linux-64::sqlite-3.33.0-h62c20be_0 tk pkgs/main/linux-64::tk-8.6.10-hbc83047_0 tqdm pkgs/main/noarch::tqdm-4.51.0-pyhd3eb1b0_0 urllib3 pkgs/main/noarch::urllib3-1.25.11-py_0 wheel pkgs/main/noarch::wheel-0.35.1-pyhd3eb1b0_0 xz pkgs/main/linux-64::xz-5.2.5-h7b6447c_0 yaml pkgs/main/linux-64::yaml-0.2.5-h7b6447c_0 zlib pkgs/main/linux-64::zlib-1.2.11-h7b6447c_3 Preparing transaction: done Executing transaction: done Miniconda3-latest-Linux-x86_64.sh: line 457: /tmp/tmp.aarljEag68/my: Is a directory [my install dir]$»>
It also incorrectly makes a second folder:
The installer is even aware of the issue but just ignores it:
I’m getting an error indicating that the file path has a space in the name when installing Anaconda on Windows 10
When installing Anaconda3 2018.12 (64-bit) on Windows 10, I’m getting an error indicating that the file path has a space in the name (‘Program Files’ directory on my C:\ drive), and that some Conda packages may have problems with this if I continue.
Does anyone know specifically which packages may have a problem? I’m using Python primarily for data science (SciPy/NumPy, Pandas, etc.).
See link for a screenshot of the warning.
3 Answers 3
what i did is: Run the installer as administrator (Right-click on installer to select run as administrator).in order to get.
this form to install the program helped me
Check that there is no space in the naming of your destination folder. Check here: https://www.youtube.com/watch?v=ejKaXo2pqwQ
And maybe, this is because it wants you to have the application stored in some directory which can be easily accessed using command prompt and which has no spaces in its name.
Actually, I was doing the same thing but in some folder named as «Setups and Applications». It created an error message saying that 2 spaces are not allowed, and so I have to do the installation in some other folder that had no space in its location. It worked fine when I selected a folder that had no space in its location.
Destination folder contains 1 space anaconda что это
I tried installing anaconda for my AI project using python. When I try to install anaconda on to my new laptop but when the prompt comes to where I should be saving my file I get this warning «Destination folder contains 1 space. This can cause problems with several conda packages. Please consider removing the space.»
I am trying to save the file on my C drive but I keep getting this warning and my laptop is also new. How do solve this issue. Please help
2 Answers 2
It might be because your username has space in it like C:\Jon Doe\Anaconda3\
Install anaconda at C:\Anaconda3\ or something
Anaconda Install: Problem with spaces
I am new to this site, so please redirect if not appropriate.
I am trying to install Anaconda in ubuntu. I want to install it on a particular path as instructed on their guide. The problem is with the path specification. I have ensured that the immediate path to the install folder does not contain any spaces. But I get
ERROR: Cannot install into directories with spaces
Now, I figured maybe any directories on the path (may not be directly entering the path name) must not contain any spaces. Is this true? In this case, I would have to manually change folder names for all! Additionally this does not seem to be true since there maybe a lot of nested folders and that would be a really cumbersome task. Any solutions or insights? I am learning this thing on the go. Any suggestions would be welcome!
I'm getting an error indicating that the file path has a space in the name when installing Anaconda on Windows 10
When installing Anaconda3 2018.12 (64-bit) on Windows 10, I’m getting an error indicating that the file path has a space in the name (‘Program Files’ directory on my C:\ drive), and that some Conda packages may have problems with this if I continue.
Does anyone know specifically which packages may have a problem? I’m using Python primarily for data science (SciPy/NumPy, Pandas, etc.).
See link for a screenshot of the warning.
3 Answers 3
what i did is: Run the installer as administrator (Right-click on installer to select run as administrator).in order to get.
this form to install the program helped me
Check that there is no space in the naming of your destination folder. Check here: https://www.youtube.com/watch?v=ejKaXo2pqwQ
I think that occurred because if you see the location of your destination folder in the image you posted in your question, it has a space in the name of "Program Files". So maybe, if you were to use command prompt or shell and for example — change directory to "Program Files", it may cause some issues in not identifying the exact directory you want it to.
And maybe, this is because it wants you to have the application stored in some directory which can be easily accessed using command prompt and which has no spaces in its name.
Actually, I was doing the same thing but in some folder named as "Setups and Applications". It created an error message saying that 2 spaces are not allowed, and so I have to do the installation in some other folder that had no space in its location. It worked fine when I selected a folder that had no space in its location.