Create github python3 branch for contributors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calibre |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I am aware that a python3 version is not currently planned due to the amount of tedious work involved in porting the code however this is a good opportunity to leverage the open source community to contribute.
Please create a development branch containing the codebase after running the 2to3 automatic upgrader (2to3 --output-
The reason I'm requesting this of you, instead of performing the upgrade on a local branch myself. is that the automatic tool produces a large number of file changes, resulting in large commits which difficult to review for malicious code if they are sent by someone as a pull request. Therefore, after the bulk of changes are made automatically, contributors will be able to send small commits to fix resulting bugs.
There is just no way that calibre is ever going to be ported to python 3. There are over half a million lines of code in calibre including lots of python C extensions. And that's not even mentioning its third party dependencies. In my experience "leveraging the open source community" is never going to work, because no one is going to do the *huge* amount of tedious work involved.
Not to mention that using 2to3 is the wrong way to go about it, since it means that the 2to3ed branch will then get out of sync with master. The only sane way to do it is to make the code base work with both pythons.