10 ms·

Yes. https://github.com/kovidgoyal/calibre/blob/master/README.python3 https://github.com/kovidgoyal/calibre/blob/master/README.pyt... https://github.com/kovid

Yes. https://github.com/kovidgoyal/calibre/blob/master/README.python3 https://github.com/kovidgoyal/calibre/blob/master/README.pyt... https://github.com/kovidgoyal/calibre/pull/870 https://github.com/kovidgoyal/calibre/pull/870 > Yeah there are not a lot of low hanging fruit left. Now one just has to get betas out and have people test them and report bugs. And plugin developers use the betas to port their plugins. But it is going to have to wait until after the webengine migration is done and calibre 4 is released.

slacka 7y ago
This is great news. Last I heard, the author of Calibre's said: > I am perfectly capable of maintaining python 2 myself. Far less work than migrating the entire calibre codebase. [1] > calibre has half a MILLION lines of python and python extension code...calibre has lots and lots of code that deals with bytes -- network protocols, binary file formats, etc. Python 3 is simply worse than python 2 for this use case. It has a crippled bytes type among other unfelicities. [2] > There is just no way that calibre is ever going to be ported to python 3. [3] Glad to see some outsider, flaviut, stepped to to the challenge and kovidgoyal accepted his pull request. Looking at the pull request it seems that kovidgoyal's fear about external native functions, network protocols, binary file formats, and python3's byte type was not so insurmountable. [1] https://bugs.launchpad.net/calibre/+bug/1714107 https://bugs.launchpad.net/calibre/+bug/1714107 [2] https://bugs.launchpad.net/calibre/+bug/1456642 https://bugs.launchpad.net/calibre/+bug/1456642 [3] https://bugs.launchpad.net/calibre/+bug/1756458 https://bugs.launchpad.net/calibre/+bug/1756458
driverdan 7y ago
870 has been open for over a year. It's clearly not high on the priority list.
- icebraining 7y ago
  Whether "a year" is high or low depends on the project in question. If you look at the commit list, py3 work seems clearly the predominant effort.

slacka 7y ago

This is great news. Last I heard, the author of Calibre's said: > I am perfectly capable of maintaining python 2 myself. Far less work than migrating the entire calibre codebase. [1] > calibre has half a MILLION lines of python and python extension code...calibre has lots and lots of code that deals with bytes -- network protocols, binary file formats, etc. Python 3 is simply worse than python 2 for this use case. It has a crippled bytes type among other unfelicities. [2] > There is just no way that calibre is ever going to be ported to python 3. [3] Glad to see some outsider, flaviut, stepped to to the challenge and kovidgoyal accepted his pull request. Looking at the pull request it seems that kovidgoyal's fear about external native functions, network protocols, binary file formats, and python3's byte type was not so insurmountable. [1] https://bugs.launchpad.net/calibre/+bug/1714107 https://bugs.launchpad.net/calibre/+bug/1714107 [2] https://bugs.launchpad.net/calibre/+bug/1456642 https://bugs.launchpad.net/calibre/+bug/1456642 [3] https://bugs.launchpad.net/calibre/+bug/1756458 https://bugs.launchpad.net/calibre/+bug/1756458

driverdan 7y ago

870 has been open for over a year. It's clearly not high on the priority list.

icebraining 7y ago
Whether "a year" is high or low depends on the project in question. If you look at the commit list, py3 work seems clearly the predominant effort.