-
-
Notifications
You must be signed in to change notification settings - Fork 324
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
White spaces not allowed in installation path #593
Comments
From 3.4.0, check_path_spaces: false |
That's amazing!!!! Have you tested that the resulting installation is functional? |
Recent conda versions do tolerate spaces in paths, so it should be ok. Anaconda itself seems to be using this option, according to OP. |
i see. i guess i'm more scare of activate / deactivate scripts not being tested with whitespace. so an "early failure" is better than a late failure in my world, but i'm ok if it comes with a huge warning. Windows has made it harder to avoid a space in your home path. I've recreated my users a few times on some computers here and there since it owuld show up as
|
Comment:
Hello,
In our corporate policies, Windows software are only allowed to be installed in "Program Files" so it's not possible to install miniforge as white spaces are not allowed in installation path (compared to Anaconda that allows it with a warning).
Is there any chance miniforge will also allow white spaces (with a warning) in the future ?
Or did miniforge allowed it before and was changed to refuse white spaces at some point ? If it's the case, which is the latest version of miniforge allowing white spaces in installation path ?
Thank you.
The text was updated successfully, but these errors were encountered: