4 ms·

There will still be batteries included. Brett (the article) was talking about how to clean it up, my point in this thread (http://mail.python.org/pipermail/stdl

by jnoller 17y ago

There will still be batteries included. Brett (the article) was talking about how to clean it up, my point in this thread (http://mail.python.org/pipermail/stdlib-sig/2009-September/000398.html http://mail.python.org/pipermail/stdlib-sig/2009-September/0...) is a break-up which still offers the batteries (as a single download file - the other downloads are "advanced"). No one wants to get rid of the batteries; we just want to move them so they are not tightly-coupled with cpython-core (meaning for instance, Jython can more easily leverage them) and we can fix/clean them up more aggressively. I completely agree with the foraging around PyPi comment - I hate doing that too, fundamentally what we all want is a cleaner, best of breed stdlib all of the implementations can share.

garnet7 17y ago
Oh, well, that sounds great then. Thanks for the reply. One thing though: you mention in your post to the ML, "removing things with low test coverage, poor docs or things which simply are not the best option". I just hope, along with that, you have the other side of the coin: liberally bring in new things which have good test coverage, good docs, and which are a pretty darn good option. :)