[Python-Dev] Re: [Python-checkins] CVS: python/nondist/peps pep-0204.txt,1.4,1.5

[Guido van Rossum]

> Shouldn't we allow other people to tweak PEP 0? It would certainly lighten
> Barry's administrative overload.
> 
> I mean, geez... this is what source control is about. Let a lot of people in
> there, but be able to back up in case somebody totally goofs it.

Agreed.

> This goes for adding new PEPs, too. I'm not as convinced here, since some
> level of "good enough for a PEP" filtering is probably desirable, but then
> again, it would seem that the people with commit access probably have that
> filter in their head anyways.

Here, common sense and good judgement should be applied.  If there
seems to be consensus that a PEP is needed, there's no need to wait
for Barry.  The update to PEP-0000 commits the assignment of the new
PEP number.  But the new PEP should follow all the rules for a new
PEP!

Having Barry in the loop makes sense for those who aren't sure they
can comply with all the rules, and for those outside the python-dev
community.

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