Skip to content

Fix --no-implicit-reexport inconsistency #11707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Dec 30, 2021
Merged

Conversation

hauntsaninja
Copy link
Collaborator

@hauntsaninja hauntsaninja commented Dec 10, 2021

Fixes #11706

@github-actions

This comment has been minimized.

@hauntsaninja hauntsaninja deleted the test branch December 10, 2021 20:29
@hauntsaninja hauntsaninja restored the test branch December 10, 2021 20:32
@hauntsaninja hauntsaninja reopened this Dec 10, 2021
@hauntsaninja hauntsaninja merged commit d168b6d into python:master Dec 30, 2021
@hauntsaninja hauntsaninja deleted the test branch December 30, 2021 21:41
tushar-deepsource pushed a commit to DeepSourceCorp/mypy that referenced this pull request Jan 20, 2022
hauntsaninja pushed a commit to hauntsaninja/mypy that referenced this pull request May 1, 2022
Fixes python#12689

We always hid e.g. `import concurrent`, but looks like mypy
never hid `from concurrent import futures`. It's possible this fix is
pretty breaking for users, let's see what primer thinks.

I last touched this logic in python#11707, which fixed cases involving
implicitly reexported symbols that shared the name of a module
hauntsaninja added a commit that referenced this pull request Jun 24, 2022
Fixes #12689

We always hid e.g. `import concurrent`, but looks like mypy
never hid `from concurrent import futures`. It's possible this fix is
pretty breaking for users, let's see what primer thinks.

I last touched this logic in #11707, which fixed cases involving
implicitly reexported symbols that shared the name of a module

Co-authored-by: hauntsaninja <>
Gobot1234 pushed a commit to Gobot1234/mypy that referenced this pull request Aug 12, 2022
Fixes python#12689

We always hid e.g. `import concurrent`, but looks like mypy
never hid `from concurrent import futures`. It's possible this fix is
pretty breaking for users, let's see what primer thinks.

I last touched this logic in python#11707, which fixed cases involving
implicitly reexported symbols that shared the name of a module

Co-authored-by: hauntsaninja <>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The behavior of --no-explicit-reexport is inconsistent/misleading
1 participant