[Python-Dev] warnings about missing __init__.py in toplevel directories

["Martin v. Löwis"]

Ronald Oussoren wrote:
> Some time ago a warning was introduced for directories on sys.path  
> that don't contain an __init__.py but have the same name as a package/ 
> module that is being imported.
> 
> Is it intentional that this triggers for toplevel imports? These  
> warnings are triggered in the build process for PyObjC, which is in  
> itself pretty harmless but very annoying.

They were very close to not being harmless earlier this year: Python
was almost changed to actually treat the directory as a package
even if it does not contain an __init__.py. In that case, the directory
itself would have been imported, not the thing inside. The warning
is (also) a hint that you should do some renaming - future versions
of Python might drop the need for __init__.

Regards,
Martin