When is PEP necessary?

[Steven D'Aprano]

On Sat, 23 Apr 2011 17:46:26 +0530, Disc Magnet wrote:

> Is PEP necessary to add a new package to the standard library?

See http://www.python.org/dev/peps/pep-0001/

 
> What if the community just wants to add a new module to an existing
> package?

"Just"? Adding a new module is a big step.

How do you know the community wants to add a new module, without a PEP? 
The purpose of the PEP is to demonstrate that the community wants the new 
module, and to ensure that there will be people available to maintain 
that module once it is added.

http://www.python.org/dev/peps/pep-0002/


> What if only a new function has to be added to a module in the standard
> library?
> 
> What if only a line or two are to be added to a function in the standard
> library?

Trivial changes do not require a PEP.

There is a procedure which is supposed to be followed for backwards-
incompatible changes (described in a PEP, naturally), but for new 
features, generally the package maintainer is free to add them without a 
PEP.



-- 
Steven