[issue2705] incompatible change to warnings.showwarning

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Thu, May 1, 2008 at 7:29 PM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > > Benjamin Peterson <[EMAIL PROTECTED]> added the comment: > > Why don't you add a Py3k warning and keep it in Py3k? Just asked python-dev if they are okay with th

[issue2705] incompatible change to warnings.showwarning

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Why don't you add a Py3k warning and keep it in Py3k? __ Tracker <[EMAIL PROTECTED]> __ ___ Pyth

[issue2705] incompatible change to warnings.showwarning

Brett Cannon <[EMAIL PROTECTED]> added the comment: Fixed in r62626. I left in the optional arguments but they are just not called anymore by the 'warnings' machinery. I might add a PendingDeprecationWarning so that people start to add the argument, though, for future use. -- resoluti

[issue2705] incompatible change to warnings.showwarning

Jean-Paul Calderone <[EMAIL PROTECTED]> added the comment: By the way, I just noticed that Lib/idlelib/PyShell.py includes an override of `showwarning´ which is defined with the old signature. I ran idle from trunk and verified that is indeed breaks warning reporting. __

[issue2705] incompatible change to warnings.showwarning

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- priority: critical -> release blocker __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mai

[issue2705] incompatible change to warnings.showwarning

Brett Cannon <[EMAIL PROTECTED]> added the comment: I have emailed python-dev to try to decide how to handle this. -- assignee: -> brett.cannon nosy: +brett.cannon priority: -> critical __ Tracker <[EMAIL PROTECTED]> _

[issue2705] incompatible change to warnings.showwarning

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Is it a theoretical case or are you thinking about a specific library Y? Also, seeing some things break when a new Python version is released is not new as you certainly know : see http://twistedmatrix.com/trac/ticket/1867 _

[issue2705] incompatible change to warnings.showwarning

Glyph Lefkowitz <[EMAIL PROTECTED]> added the comment: pitrou: You're missing a few steps. If you are maintaining project X, which depends on library Y, that adds a showwarning hook for some reason, you need to: * check out a development version of library Y, which you do not normally maintain

[issue2705] incompatible change to warnings.showwarning

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: We should have an entry under "Porting to 2.6" in whatsnew. -- nosy: +benjamin.peterson __ Tracker <[EMAIL PROTECTED]> __ _

[issue2705] incompatible change to warnings.showwarning

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Well, all you have to do is to change the hook's signature to the new one and, since the last parameter is optional, it should not cause any backwards compatibility problems. That is, the new hook should work fine on Python < 2.6 as well. Am I

[issue2705] incompatible change to warnings.showwarning

New submission from Jean-Paul Calderone <[EMAIL PROTECTED]>: In Python 2.5 and earlier, the `showwarning´ function in the `warnings´ module has this signature: def showwarning(message, category, filename, lineno, file=None): In trunk (and presumably what will become Python 2.6), this has beco