ModuleNotFoundError: No module named 'PyQt5'

[xnghu]

Description of how I can reproduce my bug:

0. Running Debian Sid. Freshly updated and upgraded as of moments before posting this.
1. Add the KXStudio repositories via kxstudio-repos.deb via https://kx.studio/Repositories
2. Update and install Carla with sudo apt-get install carla (Successfull)
3. Running Carla gives:

$ carla
Traceback (most recent call last):
  File "/usr/share/carla/carla", line 22, in <module>
    from carla_host import *
  File "/usr/share/carla/carla_host.py", line 40, in <module>
    from PyQt5.QtCore import (ModuleNotFoundError: No module named 'PyQt5'`

4. Attempting to manually install python3-pyqt5 shows it's already installed:

$ sudo apt-get install python3-pyqt5
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-pyqt5 is already the newest version (5.15.6+dfsg-1).

Expected behavior: Carla installs and works without further dependency management when using the package manager and the KX Repos.

Please let me know what other info I might provide to help solve this

[falkTX]

This is a debian problem, not Carla. If you have python3-pyqt5 installed then this simple command should run without errors:

python3 -c "import PyQt5"

[edward3h]

I ran into the same issue on Ubuntu 21.10.

The workaround was to install PyQt5 with pip: pip install PyQt5

[falkTX]

I seriously advise against that. installing pyqt through pip is likely to break many things

[edward3h]

Do you have a better suggestion?

[falkTX]

It is something to see in your own distro. installing python3-pyqt5 should not be hard, and if they broke it they really need to fix it then

[Schneckensuppe]

hi, I'm on Debian GNU/Linux 11 (bullseye), with gnome. I had the same problem, which I solved by launching "python3", you can see its default python version, for me "python3.8.9" then installing via pip pyqt5: "python3.8 -m pip install pyqt5"

[mxmilkiib]

For a more robust system, installing it via the package manager rather than pip is advised. The package manager knows nothing about what pip does, so when the package manager (and I've no idea how it didn't install it as a dependency previously) eventually tries to install the module, there will either be an error or two copies of the module on the system that could eventually go out of sync with other things and cause a problem.