option to disable mypy caching#23146
Merged
cburroughs merged 1 commit intopantsbuild:mainfrom Mar 5, 2026
Merged
Conversation
We do a lot of work (see history of mypy/rules.py) to provide a working solution for the mypy cache and to move it around between sandboxes correctly. Unfortunately, sometimes bugs in mypy or Pants prevent the cache from being viable -- see the looong journey in pantsbuild#18519 -- and the user might reasonably want to disable the cache entirely in those situation. (In my DAYJOB repo for example, the mypy sqlite cache is > 700 MiB which is a lot of write out and get no value from. They can't do --no-incremental because that still writes the cache python/mypy#19489 so we need to facilitate pointing to /dev/null
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
2 participants
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.
We do a lot of work (see history of mypy/rules.py) to provide a working solution for the mypy cache and to move it around between sandboxes correctly. Unfortunately, sometimes bugs in mypy or Pants prevent the cache from being viable -- see the looong journey in #18519 -- and the user might reasonably want to disable the cache entirely in those situation. (In my DAYJOB repo for example, the mypy sqlite cache is > 700 MiB which is a lot of write out and get no value from. They can't do --no-incremental because that still writes the cache python/mypy#19489 so we need to facilitate pointing to /dev/null