Nested packages and import order bug

[Joerg Sonnenberger]

Hi all,
I have a package a.b with the following content:

a/b/__init__.py:
  import a.b
  dir(a.b)

Running "import a.b" generates an AttributeError for b, obviously
the import didn't add b to the module "a". Even though it can be
argued that importing a package from within is bad style, this
a clearly a bug since its at least surprising.

Shouldn't the import create the namespace entry in a after it
created the module entry in sys.modules? 

Therefore should I submit a bug report?

Joerg