22 Replies
@🪶 𝕴𝖔𝖘𝖊𝖕𝖍 Best not to post your Modular auth token. That's the one that starts with
mut_. I'd redact it out if I were you.Did I do it?
Congrats @🪶 𝕴𝖔𝖘𝖊𝖕𝖍, you just advanced to level 1!
Yep
Thanks
It looks like Pika OS doesn't use apt even though it does have an Ubuntu base. Modular officially only supports a couple Ubuntu versions at the moment
Maybe you could try modifying the installer script to use pikman if it's similar enough to apt? Though that's likely a botched solution, just a thought
I'm not acquainted with Pika OS
As far as I understand, mojo uses the system python.
In the latest version of python on Linux, you cannot install packages using pip without using env, but this is very easily fixed.
Just delete 1 file
And try to run the mojo installation again.
Thanks for the fix! New one though:
Try entering
And install mojo again
Same bug
try execute
from root user
Everything went well 😄
Now I have a question
Will I only be able to use that installation in root, then?
Or is it system-wide?
Did you write the commands that the installer issued after installation?
Not yet, but it seems they tell me to use root paths
🔥 Mojo installed! 🔥
Now run the following commands if you are using bash:
echo 'export MODULAR_HOME="/root/.modular"' >> ~/.bashrc
echo 'export PATH="/root/.modular/pkg/packages.modular.com_mojo/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
If you are using ZSH, run the following commands:
echo 'export MODULAR_HOME="/root/.modular"' >> ~/.zshrc
echo 'export PATH="/root/.modular/pkg/packages.modular.com_mojo/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc
Then enter 'mojo' to start the Mojo REPL.
For tool help, enter 'mojo --help'.
For more docs, see https://docs.modular.com/mojo.
One idea, try copying .modular to your user's folder and replacing /root/ with /home/YOUR USER/
@❤🔥 I was able to get it working, thanks! 😄
I think the third line should start with a /home/ to set the "PATH"
Yeah, I forgot to add that.
I wouldn't suggest this publicly without adding a reference to what that is and what it means.
For those reading:
https://peps.python.org/pep-0668/
Since many OS depend on Python for system tasks, installing certain packages on default environment could result in conflicts that break the OS itself. For that, this feature was introduced to prevent
PIP from modifying default environment.
Few others have already made it by using venv and modifying mojo config to point to venv, which is safer on the OS.PEP 668 – Marking Python base environments as “externally managed” ...
Python Enhancement Proposals (PEPs)
Hmm, I didn’t know that python packages could somehow affect the operation of the system, I always installed the packages and there were no problems with the system.
I don't think it's that critical.
While this doesn't happen so much in the wild, it still does to a certain percentage the prompted the PSF to consider a PEP for it.
Well then you need to make an issue on Github so that they make an update for installing mojo, so that they do the installation using venv
Agree.