S
Szabolcs Nagy
Paul said:Numpy should certainly be included and I think there are efforts in
that direction. There is also a movement to choose a web framework to
include and Django might be a good choice. I think the Zope
maintainers want to keep Zope separate and I think PIL has an
incompatible license...
do not do that
(1)
i love when i can create a minimalistic system
think about it this way: what if you want to run python on an embeded/
low resource system?
if you want python to do webhosting the solution is _not_ to include
every related package
look at eg. debian: you can use it for lowresource system, desktop,
scientific computation and for webserver as well because of it's
package management system --> you can build a min. system and a huge
system as well.
(2)
seriously, python is a programming language and not a flee market (so
don't compare it to java or php)
unfortunately lots of ppl working on web related stuff think web is
the only reason a programming language should exist, which is pretty
stupid
i don't want a "webmodule" in a stdlib at all. implementing the
standards and recommendations should be enough. web in general is a
huge and ugly bloat, keep it away from a language core.
(3)
having a maintained set of modules for every possible problem is nice,
but shouldn't be a part of the core lib.
eg. numpy, mysql, ssl, pil, ... are not needed in the stdlib since
most of the programming tasks don't need those
they should be maintained separately, with an easy way to find and
install them. that's what cheese shop and distutils are for.
for me batteries included means i get a clean and consistent stdlib
and if i need special functionality i can add modules and extensions
easily
nsz