carlosperate
commented
2 years ago Possible solutions:
- Detect if Mu is running from an installer and only apply the flag in that environment
- Try to import virtualenv (or mu) with the -I flag and if it fails launch the virtualenv command without it
- Document that if a user in Debian-based distros doesn't want to user venvs they might need to pip install with the
--systemflag- This is highly discouraged, as it can mess with packages that the OS needs
- others?
Current workarounds for Linux users:
- Install the python3-virtualenv package using apt (or your OS package manager)
- Install Mu in a virtual environment, as that is the recommended way and it should work much better.
- I would also personally recommend to use pipx, as it's great for installing Python-based applications: https://pypa.github.io/pipx/
- pipx will automatically install Python applications in their own isolated virtual environment, and add the executable to the PATH so that it can be easily launched like any other app.
tmontes
rickcox
This is a follow up from the solution to:
Which was to add the
-Iflag to thepython -m virtualenv ...command: https://github.com/mu-editor/mu/pull/1921/filesThis is perfect for the installer Mu instances, as everything needed is bundled and we want to isolated from any user Python environment. However, it introduces an issue in some Linux distros, or at least Debian based ones, and maybe others too (and maybe even Windows, as it has the option to install packages in
%APPDATA%\Python, but needs to be tested).In these Python environments
pip installby default installs packages in the "user's environment" and so, they are not present to the interpreter when using the-Iflag.So when launching Mu and it tries to create a virtualenv with the
-Iflag it cannot find the module:To show this in a relatively clean Ubuntu 20.04, after running
python3 -m pip install mu-editor==1.1.0b7, these are the packages locations:Basically anything from the OS is installed in
/usr/lib/python3/dist-packagesand everything installed by the user from thepip install mu-editorcommand is in/home/parallels/.local/lib/python3.8/site-packages.Using the
-Iflag we can see that the interpreter doesn't see any of the Mu dependencies:Crash reports: