Incorrect "Module ... has no attribute"

[be9]

I've created a full repro here.

In short, there's a main module which imports some names from another package:

# planner/web.py
from planner.scheduling import RandyScheduleBuilder, ScheduleBuilder, book_campaign, cancel_campaign, reserve_campaign
#  ...

# planner/scheduling/__init__.py
from planner.scheduling.reserve import (
    book_campaign,
    cancel_campaign,
    reserve_campaign,
)
from planner.scheduling.make_schedule import (
    LowLevelSchedulingStats,
    make_schedule,
)

from planner.scheduling.lowlevel.base import ScheduleBuilder, ScheduleBuilderMaker
from planner.scheduling.lowlevel.randy import RandyScheduleBuilder

All these names are correct, however mypy --strict -p planner shows errors:

planner/web.py:1: error: Module 'planner.scheduling' has no attribute 'RandyScheduleBuilder'; maybe "ScheduleBuilder"?
planner/web.py:1: error: Module 'planner.scheduling' has no attribute 'ScheduleBuilder'; maybe "ScheduleBuilderMaker" or "RandyScheduleBuilder"?
planner/web.py:1: error: Module 'planner.scheduling' has no attribute 'book_campaign'
planner/web.py:1: error: Module 'planner.scheduling' has no attribute 'cancel_campaign'
planner/web.py:1: error: Module 'planner.scheduling' has no attribute 'reserve_campaign'

[JukkaL]

--strict defines --no-implicit-reexport, which requires exported imported names to be imported using from foo import bar as bar. The error message is confusing, however (#7251).

[be9]

@JukkaL yes, indeed, removing --strict removes the errors. However, if I keep using --strict and define __all__, errors are still there:

from planner.scheduling.reserve import (
    book_campaign,
    cancel_campaign,
    reserve_campaign,
)
from planner.scheduling.make_schedule import (
    LowLevelSchedulingStats,
    make_schedule,
)

from planner.scheduling.lowlevel.base import ScheduleBuilder, ScheduleBuilderMaker
from planner.scheduling.lowlevel.randy import RandyScheduleBuilder


__all__ = [
    'book_campaign',
    'cancel_campaign',
    'reserve_campaign',
    'LowLevelSchedulingStats',
    'make_schedule',
    'ScheduleBuilder',
    'ScheduleBuilderMaker',
    'RandyScheduleBuilder',
]

The docs say that __all__ should work.

P.S. import ... as ... works though.

[JukkaL]

__all__ works on master for me. Can you try the GitHub mypy master?

[be9]

@JukkaL yes, __all__ on master works for me too.

[stur86]

Resurrecting this old issue - I'm having this problem now, with version 0.942. Importing a module with __all__ defined explicitly and then accessing __all__ still causes a MyPy warning.