[Python-Dev] External Package Maintenance (original) (raw)

Phillip J. Eby pje at telecommunity.com
Mon Jun 12 22:06:25 CEST 2006

At 03:42 PM 6/12/2006 -0400, Edward C. Jones wrote:

Guido van Rossum wrote: > developers contributing code without wanting > to give up control are the problem.

That hits the nail on the head.

Actually it's both irrelevant and insulting.

I just want changes made by the Python core developers to be reflected in the external releases. I'd be more than happy to move the external release to the Python SVN server if that would make it happen.

If there was only one release point for the package, I would've had no problem with any of the changes made by Tim or AMK or anybody else. The "control" argument is a total red herring. If I had an issue with the actual changes themselves, I'd address it on checkins or dev, as is normal!

The "nail" here is simply that maintaining two versions of a package is awkward if changes are being made in both places. I'd love to have only one place in which wsgiref is maintained, but Python's current directory layout doesn't allow me to put all of wsgiref in "one place".

And if we hit that "nail" on the head (instead of hitting the external authors on theirs), it is a win for all the external contributors.

More information about the Python-Dev mailing list