[croniter] croniter.pyi: get_next with a ret_type passed should return that type
#14267
Conversation
This file contains hidden or 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
`get_next` with a `ret_type` passed should return that type
|
Diff from mypy_primer, showing the effect of this PR on open source code: paasta (https://github.com/yelp/paasta)
- paasta_tools/cli/cmds/validate.py:879: error: List comprehension has incompatible type List[float]; expected List[str] [misc]
+ paasta_tools/cli/cmds/validate.py:879: error: List comprehension has incompatible type List[datetime]; expected List[str] [misc]
|
their type annotation seems wrong either way... |
anentropic
changed the title
get_next with a ret_type passed should return that typeget_next with a ret_type passed should return that type
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.
I think this was maybe a typo?
Currently I am getting spurious errors from Pyright and I think it's due to this mismatch:
