Thomas Wouters wrote: > > On 5/29/06, *Fredrik Lundh* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > this is a clear case of unnecessary meddling. removing it won't remove > much code (a whopping 11 lines is dedicated to this), nor give any speed > ups whatsoever; all you're doing is generating extra work and support > issues for a bunch of third-party developers. trust me, we have better > things to do with our time. > > -1 on meddling with this before 3.0. > > > -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...)
Isn't there at least a GCC __attribute__((deprecated))? Georg _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com