[Python-Dev] rewording PEP 360

Brett Cannon brett at python.org
Tue Jun 13 02:16:08 CEST 2006

It's sounding like a rewording of PEP 360 would help this whole external
code issue.  If it was changed to say that non-API changes could be directly
checked in would that help?

That would mean the PEP would list the contact person and what external
version corresponds to what Python release.  Basic fixes would be allowed
without issue, but API changes would be discussed with the contributor.  So
the special notes section would go away and all modules would be treated the

The other option, of course, is to reject the PEP.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20060612/aeea3289/attachment.htm 

More information about the Python-Dev mailing list