Quote:
Originally Posted by KevinH
Hi,
The real issue with Python 2.7 support is that I have to maintain the quite large patch set to make sigil_bs4 possible (make BS4 polyglot). In addition, python 2.7 will be a second class citizen as they would not have access to all of the site packages that the internal python 3 embedded one has.
So removing python 2.7 would reduce to my supporting just the new bs4 functions: prettyprint, serialize, decode_xml, and my bug fixes (which I hope to upstream). I could also remove compatibility_utils.py and a few if statements and try catch pieces required to handle python class name changes and the like.
In addition, I am also worried about supporting/dealing with/answering bug reports for python interpreters set-ups not under my control given the possibility of name collisions and things, how unicode is passed to the console, handling output streams , etc.
So all in all, removing python 2.7 would be useful, but I would only do that after helping all current plugins that are python 2.7 only become polyglot if we decided to go that way.
KevinH
|
Well, most plugins appear to be python3, and Sigil's internal routines don't need to worry about python27 compatibility.
One would already have to install python himself, and as well as any additional site-packages.
So anyone who wants to use a python27 plugin would have to install bs4 himself, as well.