-
Notifications
You must be signed in to change notification settings - Fork 154
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
LazyStruct and LazySequence don't use kwargs #365
Comments
Good find! Do you feel up to the challange to fix it? I trust your code. |
LazyStruct
and LazySequence
don't use their kwargs
I assume you found this in connection to previous topic #359 |
No, actually. As part of my editor (Atom or VSCode), I run several static analysis tool/linters (pylint, flake8, autopep8) as plugins. When I opened the construct code in my editor, the linters raised some interesting warnings, including this one: "Unused argument kw". I then investigated and found that it was actually a bug and reported it. Most of the credit belongs to pylint. |
As for this bug, I'll try to fix it. |
I've fixed Can I leave that to you? |
Of course, thank you for all effort so far. |
Fixed. |
When using the Python 3.6+ keyword argument syntax to build constructs, building lazy constructs fails.
Example Code:
gives:
I would have expected the lazy versions to produce the same values as the non-lazy versions.
Especially since the docs say they are equivalent and take in kwargs:
This is a result of
LazyStruct
andLazySequence
not using theirkw
parameters at all.Credits: Discovered with help from pylint
The text was updated successfully, but these errors were encountered: