View Single Post
Old 05-25-2020, 11:42 AM   #1
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,692
Karma: 5703586
Join Date: Nov 2009
Device: many
Attention All Plugin Devs: Remove vestiges from python 2?

Hi all,
In an attempt to cleanup and simplify the code, I was planning to edit all the plugin launcher code and remove all vestiges of our former python 2.x support that still remain. Support for python 2 plugins in Sigil has long been removed so this should not impact any current plugins (or not many).

Things like compatibility-utils, unipath, all the "from __future__" stuff, would all go away and lots of py2 only code as well in sigil_gumboc, sigil_bs4, etc.

Given that Calibre now supports and desires python3 plugins as well, any plugins that shared code along these lines across the two projects should still work.

I wanted to get feedback from plugin devs first, before starting this cleanup.
And make sure they copy any needed code from plugin_launchers they still want into their own plugin projects before it starts going away.

Please let me know if you have any concerns.

Thanks,

KevinH

Last edited by KevinH; 05-27-2020 at 01:02 PM.
KevinH is online now   Reply With Quote