Docs: mention --no-silence-site-packages #16625
Open
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
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.
This changes the docs page https://mypy.readthedocs.io/en/stable/running_mypy.html#finding-imports to mention the
--no-silence-site-packagesoption.We (package maintainers of stripe-python) had been reading the description of
--follow-imports="normal"and for a long time were struggling to understand why the type errors we were seeing when running mypy locally on our project weren't showing up for our users and squaring that away with the description on the docs page. Seeing--no-silence-site-packagesmentioned on this docs page would have helped us understand this behavior sooner.