Y’know, if it comes to it, it might not be the worst idea in the world to treat the Python v3 port as a fork for the time being. That way, the still-current iteration would remain in place for 4.x users and the port could be restricted to 5.x. It’d probably require renaming the ported plugin and a couple of files (like the me.py CLI interface script) to avoid collisions, but it would mean not having to worry about Python v2 compatibility.
Like I said, just an idea, but if it helps…
Then, perhaps, if circumstances merit it and the working v3 port can be made v2-compatible, either they could be merged or the v2 edition could formally be updated to the v3 port.
Basically, I’m considering options that (a) don’t break the plugin for anyone and (b) make a working version available on calibre 5 sooner. But remember that I’m speaking as a spectator on this process.
Last edited by Rev. Bob; 09-26-2020 at 09:48 PM.
|