<br><div><span class="gmail_quote">On 5/29/06, <b class="gmail_sendername">Fredrik Lundh</b> <<a href="mailto:fredrik@pythonware.com">fredrik@pythonware.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>this is a clear case of unnecessary meddling. removing it won't remove<br>much code (a whopping 11 lines is dedicated to this), nor give any speed<br>ups whatsoever; all you're doing is generating extra work and support
<br>issues for a bunch of third-party developers. trust me, we have better<br>things to do with our time.<br><br>-1 on meddling with this before 3.0.</blockquote><br>-1 from me, too, for the same reason. It would be nice if the use of PyArg_Parse could generate a (C) compile-time warning, but since it can't, I think a runtime warning for this minor case is just overkill. (The C compile-time warning would be useful in other cases, too... hmm, perhaps we can do some post-processing of .o files, looking for deprecated symbols left undefined...)
<br></div><br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!