Upgrade to Mypy 1.14 #400
Merged
Upgrade to Mypy 1.14 #400
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
Dropping the patch part of the version spec should allow library consumers to update to mypy >=1.14.0, <2.0.0, without requiring reactivated to update first.
|
I've been bitten by this before though, where I clean .venv and get random new versions. I've been incredibly irresponsible and using just What are you using downstream? |
|
Error here is a cache issue, that I can't reproduce and happens so often. I just have to clear the GitHub cache and re-run. |
|
Ah but looks like |
silviogutierrez
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Dropping the patch part of the version spec should allow library consumers to update to mypy >=1.14.0, <2.0.0, without requiring reactivated to update first.