-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[stubgen] Improve dataclass init signatures #18430
Conversation
According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
Thanks I’ll take a look shortly. In the meantime could you check with the typeshed people that this wouldn’t crash their CI? I’m mainly concerned about pytype not accepting assignments in stubs but haven’t checked if it works correctly now. My point is if typeshed is not ready we should wait a bit here before adding this to stubgen. |
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.
Thanks, change looks good. Please check with typeshed maintainers if this is OK before merging.
To be fair I'm not too familiar with pytype. However, I don't think these assignments should be an issue. Type checkers already need to be able to parse dataclass assignment in /CC @AlexWaygood I believe you're one of the typeshed maintainers. Do you know if |
I believe pytype uses a different parser for |
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.
Seems reasonable, thank you!
Just to catch up here. We were just in the process of testing it with typeshed. Seems pytype does indeed have an issue with it, as well as flake-pyi and ruff. I don't think this is a problem though as stubgen is meant to be a starting point to iterate from. |
Remove generated incomplete
__init__
signatures for dataclasses. Keep the field specifiers instead.