[Python-Dev] Dropping externally maintained packages (Was:Please stop changing wsgiref on the trunk)
Phillip J. Eby
pje at telecommunity.com
Mon Jun 12 21:53:58 CEST 2006
At 03:29 PM 6/12/2006 -0400, Tim Peters wrote:
>That's all ordinary everyday maintenance, and, e.g., there is no
>mechanism to exempt anything in a checkout tree from reindent.py or
>PyChecker complaints.
>
>In addition, not shown above is that I changed test_wsgiref.py to stop
>a test failure under -O. Given that we're close to the next Python
>release, and test_wsgiref was the only -O test failure, I wasn't going
>to let that stand. I did wait ~30 hours between emailing about the
>problem and fixing it, but I like to whittle down my endless todo list
>too <0.4 wink>.
Your fix masked one of the *actual* problems, which was that
wsgiref.validate (contributed by Ian Bicking) was also using asserts to
check for validation failures. This required a more extensive fix. (See
my reply to your problem report.)
Your post about the error was on Friday afternoon; I had a corrected
version on Sunday evening, but I couldn't check it in because nobody told
me about any of the "ordinary everyday maintenance" they were doing, and I
had to figure out how to merge the now-divergent trees.
The whitespace changes I expected, since you previously told me about
reindent.py. The other changes I did not expect, since my original message
about the checkin requested that people at least keep me informed of
changes (as does PEP 360), so I thought that people would abide by that or
at least notify me if they found it necessary to make a change to e.g. fix
a test. Your email about the test problem didn't say you were making any
changes.
Regardless of "everyday maintenance", my point was that I understood one
procedure to be in effect, per PEP 360. If nobody's expected to actually
pay any attention to that procedure, there's no point in having the
PEP. Or if "everyday maintenance" is expected to be exempt, the PEP should
reflect that. Assuming that everybody knows which rules do and don't count
is a non-starter on a project the size of Python.
More information about the Python-Dev
mailing list