fully-qualified namespaces?

[Lenny G.]

Thanks Michael.  That's actually what I already have, e.g.,

Hippo/
  __init__.py
  HippoCrypto.py
  Potamus.py

Of course, this has the disadvantage of not really taking advantage of
the Hippo namespace -- I might as well have:

HippoCrypto.py
Hippo/
  __init__.py
  Potamus.py

or even get rid of the namespace altogether:

HippoCrypto.py
HippoPotamus.py

Since Hippo.HippoCrypto was already in the Hippo namespace (and clearly
unambiguous with the top-level Crypto namespace from python-crypto), I
thought there might be some way to use this fact to shorten up the name
by removing the redundancy (as can be done in java/C++/etc namespaces).

It sounds like you are saying that there either isn't a way to make the
interpreter utilize this type of namespace difference, or that doing so
is so convoluted that it is certainly worse than just living with
Hippo.HippoCrypto.  I can live with these facts (with a little bit of
discomfort ;) ) -- just wanted to make sure that I understood.

  Lenny G.