On Sat, 26 Nov 2005 14:44:13 -0400, bulia byak wrote:
Not so enormous if we inlclude only what WE need.
The main problem is how do you know what extension authors will want to use? Python is partly useful because of the standard library, if you start dropping parts of that library at random, Python becomes less useful and you might as well just use Lua. It's the std library rather than the interpreter itself which is large.
And disk space is cheap.
Agreed. However, memory and bandwidth still aren't for many people.
Much cheaper than the effrts of developers trying to work around innumerable incompatibilities and bugs. Given that even you cannot identify a perfect solution, I think this one is the best in the long run. Especially important is that it's actually a solution for all platforms, without which no solution is actually a solution at all.
That's true, though given the different nature of Python support on each major platform, I think we'll end up with platform specific solutions for now anyway.
Of course installers can offer the option of not installing Python if the user so desires. And/or, we could offer -with-python and -without-python installers to choose from.
This is true. Autopackage can easily cope with checking for the systems python and only downloading an included copy if it's incompatible.
thanks -mike