Setting $MODULAR_HOME to ~/.modular instead of Users/<my-user-name>/.modular causes path issues

[Moshyfawn]

I should probably create an issue ticket, but I couldn't make sure I had the issue 100% nailed down, but as the discussions in this repo are visible and quite active, I hope the right person sees this.

I've stumbled upon a behaviour where trying to install mojo on modular install mojo with mojo failed to run python, caused by setting $MODULAR_HOME to a path containing ~/ instead of Users/<my-user-name>. Running any modular command from root would give me a new ~ folder, so there's another .modular' folder in //.modular'. The same thing happened in my project folder, resulting in another ~/<my-nested-path>/<project-name>/~/.modular. This is where I'm not sure what the reason for this behaviour is and I'm creating a discussion instead of an issue: is it creating a ~/.modular folder in the path I run the command in or something else.

Hope this makes sense. Let me know if you have any further questions.

Environment:

Modular: 0.3.1 (589ce200)
Mojo: 0.6.1 (876ded2e)
Python: 3.11.7
OS: MacOS 14.2.1
Memory: 16 GiB
Architecture: aarch64