View Single Post
Old 05-27-2025, 12:46 PM   #51
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,911
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by DiapDealer View Post
I'll be honest: at this point, I wouldn't blame anyone for not worrying about providing support for pre-2.0 PyQt5. Just leave a version that still works with pre-2.0 Sigil and make a new one that works with PySide6. With the AppImage and the ability to use virtual Python environments for plugins, there's very few people that can't get PySide6 available for Sigil plugins.

Of course anyone who wants to continue using plugin_utils as a compatibility layer between the old and the new will receive bonus points!
How much of your special QApplication wrapper from plugin_utils.py is still needed?

Should we be pulling out the old PyQt5 and compatibility code just leaving PySide6 and whatever QApplication wrappering it still needed and adding the much smaller resulting plugin_utils.py to be part of Sigil's official internal plugin launcher code?

Might be a good idea.

Thoughts?
KevinH is offline   Reply With Quote