[Plugin] TagMechanic

[recook]

+1
Especially when an Ebook producer went overboard and split into hundreds of files...

[DiapDealer]

Originally Posted by recook

python3-pyqt5 v 5.15.10+dfsg-1build6 is installed, check.

Still, the PluginRunner in Sigil says on starting TagMechanic:

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

*** Linux users will have to make sure that the PyQt5 graphical python module (or PySide6 module starting with Sigil 2.0)

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.

[DiapDealer]

If you're still having trouble with this, the newly released Sigil AppImage might be the perfect workaround to your problem. It should work fine on 24.04 and it comes with its own Python environment that's ready to go (so long as you make sure to check the "Use Bundled Python" box in Sigil's plugin preferences).

[recook]

Hi,
My trouble is relative, for i have stopped trying for now, hoping for a dist-upgrade to Ubuntu 24-10 in LinuxMint, which would put PySide6 in reach.
I've seen the Sigil Appimage download, weighing in at 213 MB.
While i applaud the alternative to Snap and Flatpack, i'll pass for now.
But many thanks for the tip.

[KevinH]

FWIW, on MacOS the installed footprint of the Sigil.app is 514,158,161 bytes (519.8 MB on disk on Intel x86_64) and 501,588,228 bytes (507.3 MB on disk on Applie Silicon arm64).

Since an AppImage is on a squashed filesystem that needs no installation, its on disk application footprint is only 213MB.

So to each their own, but a fully installed 213 MB disk footprint is actually quite good for an Application that includes its own Qt, its own Python plus tk, lxml, PySide6, etc, and of course the Sigil app itself (including all translations and dictionaries). I would bet installed on Windows it is closer to the MacOS size than the AppImage size.

Update:

In case anyone is interested here is a rough break down of the main components (in K Bytes)

Sigil.app (in K)
----------------
   495416  Sigil.app

    40704     Sigil itself

   454712     Frameworks

   328144        Qt Frameworks
    87560           Primary Qt frameworks
   240584           QtWebEngineCore

   131612        Python.framework
    17332           python3.13/lib-dynload
    44980           PySide6

So fully decompressed and installed one Qt component (Qt WebEngine) is bigger than the entire Sigil AppImage footprint.

[DiapDealer]

The latest Sigil installation on Windows is pushing 400Mb.

[DiapDealer]

Originally Posted by recook

Hi,
My trouble is relative, for i have stopped trying for now, hoping for a dist-upgrade to Ubuntu 24-10 in LinuxMint, which would put PySide6 in reach.

Do you mean PySide6 is packaged in Ubuntu 24.10 repos? That would be fantastic. I don't know why distros (other than Arch) have been so hesitant to package PySide6. I assume they'll break it up into a myriad of tiny pieces like they do Qt6 itself, but even if they do, it's still progress. I sort of gave up after 24.04 came and went with no PySide6.

[recook]

Hi,

replying to several posts:

Originally Posted by DiapDealer

Do you mean PySide6 is packaged in Ubuntu 24.10 repos? That would be fantastic. I don't know why distros (other than Arch) have been so hesitant to package PySide6. I assume they'll break it up into a myriad of tiny pieces like they do Qt6 itself, but even if they do, it's still progress. I sort of gave up after 24.04 came and went with no PySide6.

Indeed they include it, and indeed they split it up, see here.

Originally Posted by KevinH

FWIW, on MacOS the installed footprint of the Sigil.app is 514,158,161 bytes (519.8 MB on disk on Intel x86_64) and 501,588,228 bytes (507.3 MB on disk on Applie Silicon arm64).

Since an AppImage is on a squashed filesystem that needs no installation, its on disk application footprint is only 213MB.

Actually, i don't know the size of my self-compiled Sigil installation, since i guess it's put in several places after `make install`.

Your point about the squash-compressed Image is thus very well made, thank you.

[recook]

Hi,

i got bitten by the Appimagelauncher bug
"AppImage Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_shall_not_be_integrated : sqfs_open_image error",
by now somewhat (in)famous.

Integrating Appimages manually by making them executable and crafting a .desktop file for ~/.local/share/applications still works though.

Will try TagMechanic with Sigil Appimage, then.

[recook]

Hi,

i used Sigil-2.5.2-x86_64_8359bb3b2474d9360933909b718b2b23.AppImage and TagMechanic_v0.6.3.zip, put the latter in its proper place ~/.local/share/sigil-ebook/sigil/plugins/TagMechanic.
Then started the Appimage and tried Plugins>Edit>TagMechanic.

Sadly, no joy:

Status: failed

Traceback (most recent call last):
File "/tmp/.mount_Sigil.joDapm/usr/share/sigil/plugin_launchers/python/launcher.py", line 141, in launch
target_script = __import__(script_module)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/.../.local/share/sigil-ebook/sigil/plugins/TagMechanic/plugin.py", line 10, in <module>
from dialogs import launch_gui
File "/home/.../.local/share/sigil-ebook/sigil/plugins/TagMechanic/dialogs.py", line 14, in <module>
from plugin_utils import Qt, QtCore, QtGui, QtWidgets, QAction
File "/home/.../.local/share/sigil-ebook/sigil/plugins/TagMechanic/plugin_utils.py", line 40, in <module>
from PySide6 import QtCore, QtGui, QtNetwork, QtPrintSupport, QtSvg, QtWebChannel, QtWidgets # noqa: F401
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'PySide6'
Error: No module named 'PySide6'

But in the mounted Appimage, i found "/usr/lib/python3.13/site-packages/PySide6".
What's up now?

[KevinH]

First manually unpacking Sigil plugins is probably not the best idea. Let Sigil install it using the Manage Plugins menu under Sigil Plugins.

Are you sure you have told Sigil to use its embedded Python interpreter?

[DiapDealer]

Make sure you've checked the box to use the bundled Python in Sigil's preferences.The TagMechanic plugin is one of many different plugins I've used to test AppImage functionality on several different distros. It should work fine.

NOTE: after checking the "Use Bundled Python" you may need to restart the Sigil AppImage.

I've no experience with AppImageLauncher. The version available for Arch is incompatible with the latest built AppImages that use a static runtime to get around fuse2 unavailability/incompatibility. I can't compile it myself either. There's a lot of work to be done with AppImageLauncher for it to be usable on many modern Linux systems in my opinion (the least of which is updating to work with Qt6). I'm honestly not sure it's worth the effort at this point.

[recook]

Hi,

Originally Posted by DiapDealer

Make sure you've checked the box to use the bundled Python in Sigil's preferences.

How right you are.

Now TagMechanic starts witout a hitch and displays its GUI.

"It's alive, ALIVE!" 8^)

Originally Posted by DiapDealer

NOTE: after checking the "Use Bundled Python" you may need to restart the Sigil AppImage.

Not here, worked without restart.

Originally Posted by DiapDealer

I've no experience with AppImageLauncher. The version available for Arch is incompatible with the latest built AppImages that use a static runtime to get around squashfs unavailability/incompatibility.

As i said, i have a manual workaround.

Now i see your UI and realize i have not yet understood how to use it...
If you already explained that somewhere, would you be so kind as to point me there?
Thanks.

[readx]

Originally Posted by DiapDealer

I've no experience with AppImageLauncher. The version available for Arch is incompatible with the latest built AppImages that use a static runtime to get around squashfs unavailability/incompatibility. I can't compile it myself either. There's a lot of work to be done with AppImageLauncher for it to be usable on many modern Linux systems in my opinion (the least of which is updating to work with Qt6). I'm honestly not sure it's worth the effort at this point.

That's why I switched to Gear Lever. Same functionality as AppImageLauncher, but constantly updated and working with all AppImages.

[DiapDealer]

I've seen Gear Lever mentioned, but I can't get past the fact that description says Gear Lever targets Flatpak usage. I'm also finding that all the various desktop integration and automatic (decentralized) appimage updating solutions sort of runs counter-intuitive to the whole "one file to rule them all" nature of AppImages in general. My only real interest in AppImageLauncher was to see how Sigil behaved with it. But to each their own!