Quote:
Originally Posted by KevinH
Hi,
One code base will now work for both, and if Sigil does package a python in the near future, it will most likely be python 3. So making KindleUnpack work on both python 2 and 3 maximizes its future usefulness to both calibre and sigil.
Also, this will also provide an example for Sigil plugin developers who want their plugins to work on both Python 2 and Python 3 as well. And it hedges our work just in case python 2's serious bugs never get fixed. Effectively it future-proofs our code.
KevinH
|
I would think it would be wiser for Sigil to bundle Python 2 since there is a lot more code out there in Python 2 then Python 3. Many people dislike Python 3 and are sticking to Python 2. Plus, porting over Python 2 code is easier then porting over Python 2 code to run on Python 3. Add to that the fact that people who program in Python 2 would then have a learning curve moving to Python 3.
To be honest, it's best to Bundle Python 2 and forget Python 3 exists.