import Python module when there is sibling file with the same name

Question

Suppose I have following files

tata/foo.py
tata/yoyo.py

foo/__init__.py
foo/bar.py

In file foo.py I do

import foo         


        

Answer 1

This seems to be a classical issue described in PEP 328

a local module or package can shadow another hanging directly off sys.path

to deal with it:

1. Code should be executed as module rather than script (-m option).

2. Use Python 3 which has so-called "absolute import behaviour" or add

   from __future__ import absolute_import