PEP 2, Procedure for Adding New Modules

[Aahz Maruch]

In article <a6cssr$dn8$1 at newshost.accu.uu.nl>,
Martijn Faassen <m.faassen at vet.uu.nl> wrote:
>
>    New functionality is commonly added to the library in the form of
>    new modules. This PEP will describe the procedure for the
>    _addition_ of new modules. PEP 4 deals with procedures for
>    deprecation of modules; the _removal_ of old and unused modules
>    from the standard library. Finally there is also the issue of
>    _changing_ existing modules to make the picture of library
>    evolution complete. PEP 3 and 5 give some guidelines on this. The
>    continued maintenance of existing modules is an integral part of
>    the decision on whether to add a new module to the standard
>    library. Therefore, this PEP also introduces concepts
>    (integrators, maintainers) relevant to the maintenance issue.

The maintainers also possess primary responsibility for determining
whether bugfixes should be backported to previous Python releases as
discussed in PEP 6.

>Maintainer(s)
>
>    All contributions to the standard library need one or more
>    maintainers. This can be an individual, but frequently is a group
>    of people such as for instance the XML-SIG. Groups may subdivide
>    maintenance tasks among themselves. One ore more maintainers shall
                                               x
>    be the _head maintainer_ (usually this is also the main
>    developer). Head maintainers are convenient people the integrators
>    can address if they want to resolve specific issues, such as the
>    ones detailed later in this document.


-- 
                      --- Aahz  <*>  (Copyright 2002 by aahz at pobox.com)

Hugs and backrubs -- I break Rule 6                 http://www.rahul.net/aahz/
Androgynous poly kinky vanilla queer het Pythonista

"Argue for your limitations, and sure enough they're yours."  --Richard Bach