Thread: 'Old' Plugins for 'Old' Calibre Versions
View Single Post
Old 02-24-2020, 04:50 PM   #4
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 74,576
Karma: 129670952
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by DiapDealer View Post
<3.99 is "old"?? Not sure why there would need to be such recent cutoff date for any plugin. My KindleUnpack plugin (a UI interface plugin) will work from calibre v0.8.60 up to the latest Python3 betas. I understand people wanting to possibly bail on supporting the old PyQt4 versions of Sigil - that's one thing. But if your plugin worked on calibre v2.0+ (the switch to PyQt5), then it should still work on the latest (python2) releases (with no porting necessary).

Getting them to work with Python 3 is another story, but other than that, I just don't see any valid reason for a currently working plugin to drop support of calibre v2.0 - to present (python 2).

What am I missing? What drastic plugin api change happened between 2.0 and 4.11?
Something changed in 4.6 that caused the KFX DeDRM plugin to no longer work. But other then that, I don't know of any other issues with Calibre from 2.0 to present (4.11.2).
JSWolf is offline   Reply With Quote