day00 automated function to install Python about bootcamp_python HOT 3 CLOSED

@Medno i tried to modify the script to make an install in a directory with spaces but the installation just won't happen (the miniconda script refuse installation with spaces). I tried to previously export a directory with spaces but no bug appeared. I just can't reproduce the bug. Adding a \ is not a problem but i want to ensure there is a bug in the first place.

Can you precise the steps needed to reproduce the bug ?

from bootcamp_python.

For example, my PATH is composed by:

.../sbin:/Applications/VMware Fusion.app/Contents/Public/:...

When I launch the automated script as it is, I get this message:

~/.zshrc:export:110: not valid in this context: Fusion.app/Contents/Public/:...

So conda will be on the PATH and we have python with the correct version. But the PATH exported is broken.
This comes from the fact that the double quotes in the script expands the PATH variable in the zshrc during the echo "export PATH=$MINICONDA_PATH..." line in set_conda function.

Then in the zshrc we got something like:

export PATH=/path:/folder/with space/foo:bar

And the environment's PATH is splitted because of this space.

from bootcamp_python.

ok, the bug will be fixed when the next merge with master occurs

from bootcamp_python.