attempt the mu-editor command to run mu locally to check the changes
What did you expect to happen?
Running Mu locally.
What actually happened?
Mu not running locally, and seeing ModuleNotFoundError: No module named 'PyQt5' in the terminal.
Operating System Version
macOS BigSur 11.6
Mu Version
v1.2.0
Other Info
It seems that the PyQt package v.5 that Mu (v1.2.0) is using for UI isn't compatible with the system architecture of newer Mac computers. Instead of the x86_64 architecture used on Intel-based Mac machines, newer Macs like the ones with M1 chip use ARMv8.5 architecture. Consequently, applications using PyQt can't be run until the package is compiled be ARM-compatible.
Gigi1111
commented
1 year ago
What were you trying to do?
Run Mu locally.
What steps did you take to trigger the issue?
git clonethe Mu repopip install -e ".[dev]"to install dependenciesmu-editorcommand to run mu locally to check the changesWhat did you expect to happen?
Running Mu locally.
What actually happened?
Mu not running locally, and seeing
ModuleNotFoundError: No module named 'PyQt5'in the terminal.Operating System Version
macOS BigSur 11.6
Mu Version
v1.2.0
Other Info
It seems that the PyQt package v.5 that Mu (v1.2.0) is using for UI isn't compatible with the system architecture of newer Mac computers. Instead of the x86_64 architecture used on Intel-based Mac machines, newer Macs like the ones with M1 chip use ARMv8.5 architecture. Consequently, applications using PyQt can't be run until the package is compiled be ARM-compatible.
Fortunately, the PyQt team developed universal binaries for both Intel and Apple Silicon hardware from version 6 of the package. At the moment, Tiego has created a workaround in the setup.py file on branch pyqt6 for Mac Silicon users to run Mu locally.
However, it hasn't been documented for contributors, so please add it to the setup section to make the contributing process smoother and easier.
Editor Log
ModuleNotFoundError: No module named 'PyQt5'