conda/menuinst

Problem with spaces in paths on windows

kalefranz opened this issue · 6 comments

mbewley commented

This makes the anaconda prompt not work at all (commands "conda" and "anaconda" are not recognised) on windows machines where there are spaces in the installation path (e.g. in the username for a default "single user" install). I think the fix should be just adding some quotes in the right place to the code that produces the shortcuts.

huguesv commented

This is a problem for the Anaconda installations we have in Visual Studio 2017. They are installed under C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64, etc

and the Anaconda Prompt doesn't work:

'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\huvalo\Documents>
msarahan commented

@huguesv, a path nested that deeply is going to cause problems with the path length limit. Have you not seen these? I'd be surprised.

I think we have addressed the space issue between recent conda releases and menuinst 1.4.11. These will be in the looming Anaconda 5.1 installers. If the VS team would like to test them, please email me - msarahan@anaconda.com

zooba commented

@msarahan Thanks, I already have access to those.

I haven't seen path length limit issues, but can't rule them out for sure. That path isn't really much deeper than C:\Users\my_username_here\AppData\Local\Continuum\anaconda3 (59 vs 66), and usernames certainly vary dramatically in length/spaces/Unicode/etc.

The only other option is a top-level install for all users (C:\Anaconda3), which I'm fine with provided the ACLs are correctly set (Administrators have full control, Everyone has read+execute). The inherited ACL when you install in the root directory is that anyone can modify the contents, which is a significant vulnerability and not an appropriate default.

huguesv commented

I tested the 5.1 installer and the prompt works after installing into C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64

Thanks!

github-actions commented

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!