On Thu, May 1, 2008 at 9:31 PM, Brett Cannon <[EMAIL PROTECTED]> wrote: > > I just closed the release blocker I created (the > backwards-compatibility issue with warnings.showwarning() ). I would > like to add a PendingDeprecationWarning (or stronger) to 2.6 for > showwarning() implementations that don't support the optional 'line' > argument. I guess the best way to do it in C code would be to see if > PyFunction_GetDefaults() returns a tuple of length two (since > showwarning() already has a single optional argument as it is). > > Anyone have an issue with me doing this? Is PendingDeprecationWarning > safe enough for 2.6? Or should this be a 3.0-only thing with a > DeprecationWarning?
I vote for a full DeprecationWarning. > > -Brett -- Cheers, Benjamin Peterson _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
