New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incompatible change to warnings.showwarning #46957
Comments
In Python 2.5 and earlier, the def showwarning(message, category, filename, lineno, file=None): In trunk (and presumably what will become Python 2.6), this has become: def showwarning(message, category, filename, lineno, file=None,
line=None):
I suggest restoring the previous signature for |
Well, all you have to do is to change the hook's signature to the new |
We should have an entry under "Porting to 2.6" in whatsnew. |
pitrou: You're missing a few steps. If you are maintaining project X,
These steps may be unavoidable if library Y has been unmaintained for a |
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 |
I have emailed python-dev to try to decide how to handle this. |
By the way, I just noticed that Lib/idlelib/PyShell.py includes an I ran idle from trunk and verified that is indeed breaks warning reporting. |
Fixed in r62626. I left in the optional arguments but they are just not |
Why don't you add a Py3k warning and keep it in Py3k? |
On Thu, May 1, 2008 at 7:29 PM, Benjamin Peterson
Just asked python-dev if they are okay with that. 2.6 could get a |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: