On Fri, Nov 13, 2009 at 1:08 AM, "Martin v. Löwis"
<martin@v.loewis.de> wrote:
> I am not an expert, I am just another python learner. These are just my
> views on the state of the standard libraries and to
> make them state-of-the-art..! ;)
If I understand correctly, you want the (current) standard library to be
separated from the Python implementation, and available separately.
Interestingly enough, people are very much split over whether that would
be a good thing or not. Some like it the way Python does, some dislike
it (and some quite strongly so).
In any case, many Python users consider it a good thing that it comes
"with batteries included", ie. with no need to add extra stuff for many
tasks.
Some of the Python maintainers have recently started objecting to this
setup, asking that the standard library should be split into separate
packages that are released and distributed independent of Python. Others
of us feel strongly that such a change should not be made.
So don't expect any immediate change to happen.
I think the recent postings on "CPAN for Python" in this list also stems
from similar thoughts. As the size of the Python std library increases,
and when it reaches a kind of implosion point (perhaps it is there already),
it does make sense to split it into some thing like a "core" group of
modules and add-ons which could be updated dynamically as and when
required by a tool.
It could be something as simple as a "require" keyword which could
pull in the depdencies if not found. Perhaps at the top of your module,
require (stuff, '1.27')
import stuff
Anyone who takes a quick look at the Python std library now is
sure to feel that there is an overkill of stuff there, which could be
classified and packaged better than dumping into the language
build.
Regards,
Martin