RetroSearch Browse

Sun Mar 8 19:37:22 CET 2009 · https://mail.python.org/pipermail/python-dev/2009-March/086936.html

Martin v. Löwis <martin at v.loewis.de> wrote:

> > If a library is well maintained then there seems to be little point in
> > moving it into the standard library as it may actually be harder to
> > maintain
> 
> It depends. For quickly evolving libraries, it might be harder to
> maintain them in the core, as you can't release as quickly as you
> desire. In other cases, it simplifies maintenance: whenever a
> systematic API change is added, all standard library modules get
> typically updated by whoever makes the systematic change. That is
> more productive than having each individual maintainer to figure out
> what to change in response.

This is a complicated issue.  But two sub-threads seem to be about (1)
modules dependent (or wrapping) a large, complicated third-party library
under active development, and (2) hard-to-routinely-test modules, like
imaplib.

Bill

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2009-March/086936.html below:

[Python-Dev] Integrate BeautifulSoup into stdlib?