Thread: How will Calibre handle Calibre 5 only plugins?
View Single Post
Old 01-11-2021, 05:38 PM   #2
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,754
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
What happens if a plugin that was written before Calibre 5 ends up no longer working on Calibre 4.23 because of no longer being Python 2 compatible? How will Calibre handle it?

As I see it now, Calibre 4.23 or earlier will pull up a notification that there is a new version, the new version will be installed and screw with the existing version.

Will Calibre be modified such that it will handle this issue and not show plugins that only work on Calibre 5 to Calibre 423 or earlier versions?
I would suspect that the plugin would list calibre 5+ as a prerequisite. One example would be:
Code:
    minimum_calibre_version = (5, 0, 0)  # Python 3.
So the calibre5+ version of the plugin would not install.
DNSB is offline   Reply With Quote