4 ms·
However it seems that people are slowly migrating Calibre to Python 3. Also looks like any Python3 patch doesn't break the current Calibre build is welcome ind
by bayindirh 8y ago
However it seems that people are slowly migrating Calibre to Python 3.
Also looks like any Python3 patch doesn't break the current Calibre build is welcome indeed.
- ascii_only 8y agoYes. I should have been more clear. He is not against python3 but thinks that it is less work to maintain python2 than port calibre to newer version.
- qwerty456127 8y agoThis sounds like Calibre codebase is a mess that needs to be refactored.
- darkpuma 8y agoTo be honest the best part of Calibre, the `ebook-convert` tool, is already broken out from the rest of it. It's similar to pandoc though in my opinion often does a nicer job.
- PurpleRamen 8y agoEven the best codebase can't effortless be ported. Calibre seems to have something around 25 MB of python-code, several external plugins, some C-code and other languages. Transition of this would take quite some time. Additionally, there is the problem of compability. Configuration in Calibre is python-code, and on several corners the user can mod stuff. Any transition would need to make sure to not brake things to hard.
- megablast 8y agoOh. Like every single codebase ever then?