Fix daemon false positives related to module-level __getattr__ #16292
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.
In some cases, mypy daemon could generate false positives about imports targeting packages with a module-level
__getattr__
methods. The root cause was that themypy.build.in_partial_package
function would leave a partially initialized module in themodules
dictionary ofBuildManager
, which could probably cause all sorts of confusion. I fixed this by making sure that ASTs related to temporaryState
objects don't get persisted.Also updated a test case to properly delete a package -- an empty directory is now actually a valid namespace package, so to delete a package we should delete the directory, not just the files inside it.