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.
Description
Mypy itself has a rather slow release cadences. A while ago I created mypy-dev. A repository setup to create development releases of mypy available on PyPI. Initially it was only really intended for use during the Home Assistant development. Today, I also setup a pre-commit mirror at mypy-dev-pre-commit so we could also use it here in pylint.
It wouldn't be worth it here usually, but I recently fixed a few mypy issues with the match statement which would be useful here. Once the next version is released, we could switch back again.
Note
Due to the increased release frequency and storage limits, I delete old versions on PyPI from time to time.
At most this would probably mean the mypy pre-commit check would fail if an old commit is checked out at some point. For the main branch pre-commit autoupdate should work fine.
I'd also recommend that the maintenance branch doesn't switch to mypy-dev since autoupdate isn't run there.
Resolves #10514 (comment)