-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
1.1.384 forbids ellipsis defaults in NamedTuple stubs #9191
Labels
addressed in next version
Issue is fixed and will appear in next published version
bug
Something isn't working
regression
Comments
This is #9189. |
It actually isn't #9189, that is a separate issue. Please reopen, sorry for the churn. |
1 task
erictraut
added a commit
that referenced
this issue
Oct 11, 2024
…es `...` as a default value in a stub file. This addresses #9191.
Thanks for the bug report and apologies for the regression. This issue was specific to stubs, so it wasn't covered by pyright's unit tests. This will be addressed in the next release. |
erictraut
added
the
addressed in next version
Issue is fixed and will appear in next published version
label
Oct 11, 2024
This is addressed in pyright 1.1.385. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
addressed in next version
Issue is fixed and will appear in next published version
bug
Something isn't working
regression
Describe the bug
Cf. python/typeshed#12764. When trying to update pyright from 1.1.383 to 1.1.384 in typeshed, it reports NamedTuples that use ellipses as defaults:
Causes:
Similar to function defaults, NamedTuples can have complex defaults that can't be represented statically in stubs and should use an ellipsis instead.
The text was updated successfully, but these errors were encountered: