[Python-Dev] Dropping externally maintained packages (Was:Please stop changing wsgiref on the trunk)

Brett Cannon brett at python.org
Mon Jun 12 20:26:32 CEST 2006

On 6/12/06, Fredrik Lundh <fredrik at pythonware.com> wrote:
> Brett Cannon wrote:
> > But I don't think this is trying to say they don't care.  People just
> want
> > to lower the overhead of maintaining the distro.
> well, wouldn't the best way to do that be to leave all non-trivial
> maintenance of a
> given component to an existing external community?
> (after all, the number of non-python-dev python contributors are *much*
> larger
> than the number of python-dev contributors).
> I mean, we're not really talking about ordinary leak-elimination or
> portability-fixing
> or security-hole-plugging maintenance; it's the
> let's-extend-the-api-in-incompatible-
> ways and fork-because-we-can stuff that I'm worried about.

Well, I don't know if that is necessarily the case.  PEP 360 doesn't have a
single project saying that minor fixes can just go right in.  If we want to
just change the wording such that all code in the tree can be touched for
bug fixes and compatibility issues without clearance, that's great.

But Phillip's email that sparked all of this was about basic changes to
wsgiref, not some API change (at least to the best of my knowledge).

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

More information about the Python-Dev mailing list