Hi,
Sorry but we (user-none, DiapDealer and I) have discussed this and we disagree completely with you. We don't have the huge python2 codebase to worry about like calibre does, and serious bugs in python 2 are simply not being fixed. So if we include python 3 into Sigil but write code that works on both, then we really have the best of both worlds. We can allow an external Python 2 interpreter to be used with Sigil and still bundle Python 3 internally with Sigil.
And fwiw, most plugins are not as extensive as KindleUnpack, so porting them to work on both Python 2 and 3 will not be as hard. It is not like we are mandating code that only works on Python 3 or dropping support for Python 2.
KevinH
Quote:
Originally Posted by JSWolf
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.
|