-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
get_argument_from_call
doesn't account for **kwargs
#7761
Comments
I'd like to work on this if there are nobody else~ |
Terrific. Thanks for volunteering. |
Hi @LeetaoGoooo, just an update. #8728 did a good portion of this issue, so I'll just pick up from here and look at the remaining false negatives. Let us know if you want any direction about something else to help out with! |
These mostly solve false negatives for various checks, save for one false positive for `use-maxsplit-arg`. Closes pylint-dev#7761
Thank you for letting me know about the progress on the issue. I'm glad to hear that #8728 was able to address a good portion of it. If there's anything else you think I can help with, please don't hesitate to let me know. |
Bug description
get_argument_from_call
doesn't account for keyword arguments provided by unpacked kwargs. This is causing both false positives and false negativesFalse negative
False positive
Configuration
No response
Command used
Pylint output
first example: nothing
Expected behavior
first example: Expected a warning for
bad-open-mode
Pylint version
OS / Environment
No response
Additional dependencies
No response
The text was updated successfully, but these errors were encountered: