[madhatta]

Originally Posted by davidfor

You misunderstand. The distro versions of calibre have problems. The distro maintainers change things. Or they package wrong versions of libraries. In this case, you are attempting to run a version of calibre that is not fully compatible with Python 3. It is intended to be used with Python 2.7. Kovid has been moving towards Python 3 for nearly a year, but, it is not complete. And potentially won't be until version 5 is released.

The version of the plugin I posted should compatible with Python 3 versions of calibre. Or at least the beta builds that Kovid has produced. I was swapping between the release and the beta when I was doing the testing. But, I have only tested on Windows 10 with the 64bit version. But, I won't be at all surprised if we have still missed something.

The problem with Obok was due to all this. It was a plugin that wasn't completely converted to Python 3 running in a version of calibre built for Python 2.7 but running in Python 3.

Everything you say makes sense, and thanks for writing it - and for the other work on this plugin, which you do out of the goodness of your heart. I quite acknowledge that you owe nobody anything in respect of it.

Nevertheless, an unwillingness to support your plugin in the context of calibre as it is used by many people will simply mean that less people can use your plugin, which is a shame. That doesn't place any obligation on you: as I say, you're doing this out of the goodness of your heart, and how you do it is entirely up to you. I'm just letting you know that when you make people choose between running your (excellent) plugin, and running the distro version of calibre, some will for very good reasons choose to stick with the distro version of calibre.

With that combination, are you sure surprised that it didn't work?

Surprised? No; it's free software, I expect it to break. But apparently the developers didn't think that the desire to have it work on my system was an unreasonable one.