packageless modules == pure evil?

[Bill Baxter]

I would just like to confirm with others that this is the case, and also 
perhaps raise general awareness about the issue.

The issue is that modules without a package will conflict with a 
similarly named module in _any_ package.

So for example if there's a module called "foo" and you import it in 
your project, then your project absolutely CANNOT have another module 
named "foo" or "blarf.foo" or /anything/ that ends in ".foo" anywhere in 
the import chain.

For this reason it must be concluded that packageless modules are pure 
evil, and should never ever be used.  Always always give your modules a 
package even if it's just repeating the module name like "foo.foo".

Am I right about this?
(and anyone know if module "foo.bar" will clash with "baz.foo"?)

--bb