[stubtest] Test NamedTuple definitions with default fields
#15774
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AlexWaygood
reviewed
Jul 29, 2023
AlexWaygood
reviewed
Jul 29, 2023
There was a problem hiding this comment.
It might also be worth adding some tests where the runtime uses collections.namedtuple (but the stub uses typing.NamedTuple), while we're here? You generally only create stubs for a package if that package doesn't have type annotations, so it's more common with code stubtest is running on for the runtime to be using collections.namedtuple
|
More |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a test case for #15680 from
stubtest's point of view.