[Python-Dev] External Package Maintenance

Guido van Rossum guido at python.org
Mon Jun 12 22:01:06 CEST 2006

On 6/12/06, Edward C. Jones <edcjones at comcast.net> wrote:
> Guido van Rossum wrote:
>  > developers contributing code without wanting
>  > to give up control are the problem.
> That hits the nail on the head. If something is added to the standard
> library, it becomes part of Python and must be controlled by whoever
> controls Python. Otherwise there will be chaos. If a developer puts his
> code into the standard library, it may or may not increase their status,
> ego, or income. Each developer must decide for himself.
> I suggest that the BDFL make a Pronouncement on this subject.

I think I pretty much did already -- going forward, I'd like to see
that contributing something to the stdlib means that from then on
maintenance is done using the same policies and guidelines as the rest
of the stdlib (which are pretty conservative as far as new features
go), and not subject to the original contributor's veto or prior
permission. Rolling back changes without discussion is out of the
question. (Sometimes it's okay to roll back a change unilaterall, but
that's pretty much only if it breaks the unit tests and the original
author does not respond to requests to fix his mistake within a
reasonable time.)

--Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-Dev mailing list