Quote:
Originally Posted by Thasaidon
I just installed Tag Mechanic v0.5.0.
When I ran it via Calibre this error message immediately popped up.
Spoiler:
Status: failed
Traceback (most recent call last):
File "C:\Users\ryzen\AppData\Local\sigil-ebook\sigil\plugins\TagMechanic\dialogs.py", line 15, in <module>
from PySide2.QtCore import Qt, QByteArray, QCoreApplication, QLibraryInfo, QTimer, QTranslator, qVersion
ModuleNotFoundError: No module named 'PySide2'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Prog1\Sigil\plugin_launchers\python\launcher.p y", line 134, in launch
target_script = __import__(script_module)
File "C:\Users\ryzen\AppData\Local\sigil-ebook\sigil\plugins\TagMechanic\plugin.py", line 10, in <module>
from dialogs import launch_gui
File "C:\Users\ryzen\AppData\Local\sigil-ebook\sigil\plugins\TagMechanic\dialogs.py", line 22, in <module>
from PyQt5.QtCore import Qt, QByteArray, QCoreApplication, QLibraryInfo, QTimer, QTranslator, qVersion
ImportError: DLL load failed: The specified procedure could not be found.
Error: DLL load failed: The specified procedure could not be found.
|
I have a feeling PyQt5 plugins have always been a bit flaky when run in Sigil spawned by Calibre prior to Sigil v1.3. I know they were always flaky when using an external Python interpreter on Windows. prior to v1.3.
I believe
this to be the commit (first appearing in v1.3) that fixes the issue.
The bottom line is that I can't time travel.
The 0.5.1 version of TagMechanic will work for you if you don't launch Sigil from calibre. The ability to run the new TagMechanic (or any other PyQt5 plugin) in a Sigil launched by Calibre's Open With will be waiting for you whenever you update to Sigil v1.3+