We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The new python3 construct to ensure force people to use keyword arguments without having to specify defaults is to put a bare asterisk.
Right now, if any of the files in our import chain use that syntax, it seems to break codeintel altogether.
See this stack overflow link for the exact syntax: https://stackoverflow.com/questions/2965271/forced-naming-of-parameters-in-python/14298976#14298976
I think it would be safe to just search for and drop the bare * in function definitions for codeintel's purposes.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The new python3 construct to ensure force people to use keyword arguments without having to specify defaults is to put a bare asterisk.
Right now, if any of the files in our import chain use that syntax, it seems to break codeintel altogether.
See this stack overflow link for the exact syntax:
https://stackoverflow.com/questions/2965271/forced-naming-of-parameters-in-python/14298976#14298976
I think it would be safe to just search for and drop the bare * in function definitions for codeintel's purposes.
The text was updated successfully, but these errors were encountered: