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 |
|
Could you share any more info about building the installer to allow spaces? I cloned this repo, added the line Full outputI tried to resolve this by removing conda from the base environment by removing |
|
Yea it's a bit tricky, now that I recall: conda/constructor#449 (comment) You can patch this block out and assume the risk, though. |
|
Thanks. If I only want to use mamba, is that likely to work? Or, is there a way to exclude conda from the base environment and only use mamba? |
|
I think mamba 2.x does not suffer from this problem, so go for it. This {% set name = os.environ.get("MINIFORGE_NAME", "Miniforge3") %}
{% set version = os.environ.get("MINIFORGE_VERSION", "24.9.0-0") %}
# when mamba_version is updated here, also update MICROMAMBA_VERSION in scripts/build.sh
{% set mamba_version = "2.0.2"%}
name: {{ name }}
version: {{ version }}
company: conda-forge
channels:
# specifying the channel with the full URL adds two channels
# when the end user adds the channel without the full URL
# - https://conda.anaconda.org/conda-forge
- conda-forge
write_condarc: True
# keep pkgs for space-saving implications for hardlinks when create new environments
# and keep the same with Miniconda
keep_pkgs: True
# During the interactive installation, these variables are checked.
# During batch installation, conda is never initialized
initialize_conda: False
initialize_by_default: False
user_requested_specs:
- python 3.12.*
- mamba >={{ mamba_version }}
- pip
specs:
- python 3.12.*
- mamba {{ mamba_version }}
- pip
virtual_specs:
- __glibc >=2.17 # [linux]
- __osx >=10.13 # [osx]But at that point, why not use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: