+6
Kenny Levinsen 5 years ago • updated 5 years ago 2
This would allow for use of external libraries, like pyexpat used by elementtree and xml.sax parsers, without having to compile them into the builtin parser.
While it would probably mean that the interpreter wouldn't be as "clean" as sublime's, it would allow more flexibility. People would also be able to use 2.7 if they felt like it by selecting a different interpreter, living with the consequences of some potentially broken plugins.

While I like that the builtin interpreter is small and clean, I would prefer to be able to customize the modules, or versions, used by sublime. Seeing that is already the case on OS X, I believe that it has been proved to be a working solution, and should be ported to Linux as well.

(I personally use Sublime on both Linux (for work) and Mac OS X (private), and it bugs me that I have more freedom to write plugins on OS X, meaning my awesome (heh) plugins can't be used on Linux, without finding alternative methods to do a lot of things that rely on external non-py modules.)
If not this, then at the very least I think 2.7 should be used internally instead of 2.6 
I agree that 2.7 would be more interesting than 2.6.
2.7 brought quite a few "convenience" updates, and have broader support... And seeing we use an internal interpreter, nothing really sets the limit. OS X bundles 2.7 as well, so there wouldn't be an issue there either. 2.7 is simply better.
I still think that an external interpreter on linux would makes things more fun... One can hack around the limits of the modules, but it does set a few limits... If not on functionality, at least on the ease of development.