error at "import anydbm"

Paul McGuire ptmcg at
Tue Jan 13 23:27:45 CET 2004

"Peter Hansen" <peter at> wrote in message
news:4004482A.A66C2886 at
> Generally speaking, you should try to avoid using the same names as
> the standard library modules for your own code.
This is an understandable limitation, but for new (and some not-so-new)
Python users, it is not always obvious what module names to avoid.

What if the standard library modules were put into a "std" package, to help
get them out of the global import namespace?  (Of course, this would break
*scads* of code, so maybe should be deferred to 3.0.  Or for migration
purposes, implement this in a 2.x release, and provide shadow xxx imports
that import the modules.)

-- Paul

More information about the Python-list mailing list