[Python-Dev] Please stop changing wsgiref on the trunk

Guido van Rossum guido at python.org
Mon Jun 12 18:04:53 CEST 2006

On 6/11/06, Phillip J. Eby <pje at telecommunity.com> wrote:
> As requested in PEP 360, please inform me of any issues you find so they
> can be corrected in the standalone package and merged back to the trunk.
> I just wasted time cutting an 0.1.1 release of the standalone wsgiref
> package only to find that it doesn't correspond to any particular point in
> the trunk, because people made changes without contacting me or the
> Web-SIG.  I then spent a bunch more time figuring out how to get the
> changes out and merge them back in to the standalone version such that the
> Python trunk has a specific version number of wsgiref.  Please don't do
> this again.
> I appreciate the help finding bugs, but I'll probably still be maintaining
> the standalone version of wsgiref for a few years yet.

Phillip, Please consider the burden for Python developers who have to
remember who owns what code. I know we have PEP 360, but the more I
think about it, the more I believe it's unreasonable to have growing
amounts of code in the Python source tree that cannot be modified by
Python developers who are taking the usual caution (understanding the
code, running unit tests, being aware of backwards compatibility
requirements, etc.).

Once code is checked into Python's source tree, change control should
ideally rest with the Python developers collectively, not with one
particular "owner".

IOW I think PEP 360 is an unfortunate historic accident, and we would
be better off without it. I propose that we don't add to it going
forward, and that we try to get rid of it as we can.

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

More information about the Python-Dev mailing list