Quote:
Originally Posted by recook
python3-pyqt5 v 5.15.10+dfsg-1build6 is installed, check.
Still, the PluginRunner in Sigil says on starting TagMechanic:
Code:
Status: failed
Traceback (most recent call last):
...
ModuleNotFoundError: No module named 'PySide6'
Error: No module named 'PySide6'
|
Not quite "check" on that bit. You seem to have missed the part where pytqt5 was only supported
before Sigil 2.0
Quote:
|
*** Linux users will have to make sure that the PyQt5 graphical python module (or PySide6 module starting with Sigil 2.0)
|
Quote:
Originally Posted by recook
python3-pyqt6 v 6.6.1-2build4 installed, check.
libqt6core6t64:amd64 v 6.4.2+dfsg-21.1build5 installed with lots of libqt6... dependencies, check.
Is that 6.4.2 < 6.5.2 perhaps the cause?
|
No. That's not the cause. The cause is that the TagMechanic plugin requires PySide6 starting with Sigil 2.0+. Not PyQt5, and not PyQt6. PySide6.
If you don't wish to override your distro's desire to control if/how you install extra modules into your system python, I'm afraid creating a virtual Python environment for Sigil plugins is just about your only recourse at the moment.
https://github.com/Sigil-Ebook/Sigil...Environment.md
I'm not sure why distros are choosing not to provide pyside6 packages to complement the Qt6 packages they provide. It's not as if PySide6 and PyQt6 cannot coincide.
The move to use PySide6 in Sigil plugins was done a long time ago in Sigil. Long before distros decided to start scaring their users into not using pip to install extra modules into their system pythons. Unfortunately, that move made it necessary for average users to grasp the concept of creating/maintaining multiple virtual Python environments for this sort of thing.