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 same.

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

-Brett
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to