-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-35178: Pass positional arguments to formatwarning(). #10343
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
Conversation
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for your contribution, we look forward to reviewing it! |
CLA has been signed separately |
Please open an issue on the bug tracker and describe how to reproduce the error. |
|
Hey @vstinner , any update on merge? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please write a test checking that replacing warnings.formatwarning() with a new function, and the last parameter of this function is not called 'line', still works.
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase And if you don't make the requested changes, you will be poked with soft cushions! |
Hi guys, Grammatically, there is nothing that prevents specifying the last argument with keyword
I believe the above patch was responsible for the error I got (can't see straight how though). I removed the monkey patch, and it's working fine now. So, you are welcome to close the PR w/o merging. |
https://bugs.python.org/issue35178 is a real bug and I like your fix, but a test must be written. Do you want to write a test? If not, I can ask someone else to do it. |
Hi @vstinner , based on my timing, I am unable to make a promise. So, please feel free to ask someone. Thanks! |
Thanks @tashrifbillah! I merged PR #12033 written by @tirkarthi based on this PR. |
The last argument should be
msg.line
. Havingline=msg.line
generates an error message:got an unexpected keyword arugument line=msg.line
Compare with Ln 99, the discrepancy should be apparent.
https://bugs.python.org/issue35178