[Python-Dev] External Package Maintenance

Phillip J. Eby pje at telecommunity.com
Tue Jun 13 01:23:36 CEST 2006

At 12:56 AM 6/13/2006 +0200, Martin v. Löwis wrote:
>Fredrik Lundh wrote:
> >> I just want changes made by the Python core developers to be reflected in
> >> the external releases.
> >
> > and presumably, the reason for that isn't that you care about your ego,
> > but that you care about your users.
>For that, yes. However, the reason to desire that no changes are made
>to Python's wsgiref is just that he wants to reduce the amount of work
>he has to do to keep the sources synchronized - which reduces his amount
>of work, but unfortunately increases the amount of work to be done for
>the other python-dev committers.

I see *now* why that would appear to be the case.  However, my previous 
assumption was that if somebody found a bug, they'd tell me about it and 
I'd do the work of fixing it, updating the tests, etc.  In other words, I 
was willing to do *all* the work, for changes that made sense to wsgiref.

What I didn't really "get" until now is that people might be making 
Python-wide changes that don't have anything to do with wsgiref per se, and 
that is the place where the increased work comes in.

This should definitely be explained to authors who are donating libraries 
to the stdlib, because from my perspective it seemed to me that I was 
graciously volunteering to be responsible for *all* the work related to 

(And yes, I understand now why it doesn't actually work that way.)

More information about the Python-Dev mailing list