RFC: rename environment folder?

[drammock]

I noticed that we're creating $HOME/Scientific-Python/X.X.X_X for our environments, and also ~/Documents/scientific-python for user notebooks. To avoid potential user confusion, maybe the former should be $HOME/Scientific-Python-Environments instead?

[matthew-brett]

It's a bit more complicated for Mac at least, because we create stuff in the $HOME/Applications/Scientific-Python folder, and the user would not expect to put work files there.

[matthew-brett]

Windows installs into ~/Scientific-Python, like Linux. I think I'm OK with ~/Documents/scientific-python, but I could also live with ~/Scientific-Python-Workdir or something like that. I still think ~/Documents/scientific-python is better, because Mac and Windows users will know to look there - because there is a shortcut to Documents in Finder and Windows Explorer.

[drammock]

I think I'm OK with ~/Documents/scientific-python, but I could also live with ~/Scientific-Python-Workdir or something like that.

I was proposing to rename the other one (where we store the environment, not where we default to storing user notebooks). Mostly, I want (Linux) users to avoid having two very similarly-named folders:

• ~/Scientific-Python and
• ~/Documents/scientific-python

...and having them get confused when they browse into the first one and don't see their notebooks in there. I think for macOS the status quo is fine --- users shouldn't expect to find their documents/notebooks in $HOME/Applications/[something]. But I'd argue that for both Windows and Linux it's easy, helpful, and harmless to change the install dir name to Scientific-Python-Environment or so.

[matthew-brett]

Ah - yes - sorry - I see what you mean, and you're right - something like Scientific-Python-Environments would be sensible.

[drammock]

closed by #14