-
Notifications
You must be signed in to change notification settings - Fork 35
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
False positive Unexpected keyword argument #132
Comments
I can confirm that. I think this has been the case with the extension all along. A tip as better workaround, open the Command Pallet ( |
Pylint might be caching something for faster linting. Having to restart linter each time does not feel right. /cc @DanielNoord |
|
Duplicate of #129 See discussion here for details #129 (comment). Since pylint is run in a server like manner there is some caching. This is a side effect of that. |
Hi, first of all sorry if I am not making the error report correctly.
Since a week more or less we are having problems with pylint.
If we modify one function adding an additional parameter, calls to this function from other file can not see the new parameter and pylint show the error "Unexpected keyword argument".
Only restarting VSCode the new parameter is saw by pylint.
Thank you!
The text was updated successfully, but these errors were encountered: