[stdlib-sig] Breaking out the stdlib

Antoine Pitrou solipsis at pitrou.net
Mon Sep 14 18:53:27 CEST 2009


Le lundi 14 septembre 2009 à 12:19 -0400, Jesse Noller a écrit :
> Sure, having batteries is fantastic. Until you being to realize that
> some modules are broken, not up to date with current technology, etc,
> etc. We have to be aggressive with cleaning it up.
[...]
> 
> Things within the stdlib must have a high quality bar, and should
> really represent the "one way of doing something" - meaning best of
> breed, high quality, idiomatic, etc.

Have you read the thread about argparse and the deprecation of other
modules?

You are conflating two things:
1. the presence of somewhat outdated or too low-level modules
2. the desire to have best-of-breed options available in the stdlib

We can do 2. without undoing 1. As Marc-André pointed out, even in py3k
we only deprecated a handful of very marginal modules. Emphasizing the
right modules in the documentation is probably a reasonably good answer
to the problem of having several modules fulfilling the same needs. No
need to go on a deprecation frenzy and start annoying the two thirds of
our user base just because we decided to be pure rather than practical.





More information about the stdlib-sig mailing list