Support handling implicit dependencies from `__init__.py`

[msu-reevo]

We recently saw issues with implicit dependencies being imported from __init__.py

Example:

• app/module/__init__.py
• app/module/workflows/fragile.py
• the second one will implicitly import anything from the __init__.py which the person in the fragile.py is not aware of from reading the code.

Would love to be able to report the implicit dependencies or block imports or apply layer or import rules to them.

[emdoyle]

I'd like to support this, but I also want to make sure that it is implemented in a reasonable way. If this were available as a global opt-in, would you enable it?

My main concern is that this would be 'noisy' if any __init__.py files use the relatively common pattern of 're-exporting' members from all its child modules e.g.

from .submodule1 import SubModuleOne
from .submodule2 import SubModuleTwo
from .submodule3 import SubModuleThree

With the option on, any instance of that pattern would indicate to Tach that all three submodules depend on each other (if I understand correctly). Could you tell me more about the case you would want to cover? Or maybe you would expect to configure it a bit differently?