[red-knot] Do not merge: Run ecosystem checks with 3.9#17404
Closed
[red-knot] Do not merge: Run ecosystem checks with 3.9#17404
Conversation
ef6ada9 to
683f065
Compare
Contributor
|
4fde5a2 to
184c46b
Compare
184c46b to
4247a4d
Compare
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
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.
Summary
Just a stupid way to run the ecosystem checks with 3.9 instead of 3.7 (see #17402 (comment) for details). We obviously want to fix this in another way, but this should allow us to see the mypy_primer diff.