On 6/12/06, <b class="gmail_sendername">Fredrik Lundh</b> <<a href="mailto:fredrik@pythonware.com">fredrik@pythonware.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Brett Cannon wrote:<br><br>> But I don't think this is trying to say they don't care. People just want<br>> to lower the overhead of maintaining the distro.<br><br>well, wouldn't the best way to do that be to leave all non-trivial maintenance of a
<br>given component to an existing external community?<br><br>(after all, the number of non-python-dev python contributors are *much* larger<br>than the number of python-dev contributors).<br><br>I mean, we're not really talking about ordinary leak-elimination or portability-fixing
<br>or security-hole-plugging maintenance; it's the let's-extend-the-api-in-incompatible-<br>ways and fork-because-we-can stuff that I'm worried about.</blockquote><div><br><br><br>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.
<br><br>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).<br><br>-Brett<br> </div></div>