Docs: show how --no-implicit-reexport
handles from X import Y as Z
#11083
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
In our testing, mypy appears to treat code like this as an implicit re-export. If
--no-implicit-reexport
is given, mypy will disallow it.Even though it treats code like this as an explicit re-export:
For stub files specifically, PEP 484 has this note, emphasis mine:
I am therefore assuming that this mypy behavior is intentional. (Even though I find it unfortunate and surprising, and even though
--no-implicit-reexport
seems meant for more than just stub files.) So this PR documents it.Test Plan
--no-implicit-reexport
, that would be helpful.