[ZODB-Dev] ImportError: cannot import name Interface

[Tim Peters]

[Christian Robottom Reis]
> I agree; however, isn't it a fair assumption that the main issue between
> PythonCAD and ZODB will be shared namespaces, since there is conceivably
> little else PythonCAD *can* do that affects the ZODB (apart from erasing
> glibc when setup.py install is done <wink>)?

I don't want to think about it -- I have too much else to do.  If you
*tried* it, and it worked (and you did, and it did), that cuts off a world
of idle speculation.  If someone still has problems, please work up a patch
to resolve them.

> The file BTrees/Interfaces.py also contained an unqualified import of an
> Interface package (from Interface import Interface) -- I didn't check if
> you took care of that as well. That file doesn't seem to be hugely
> important, though.

As I said, BTrees/Interfaces.py has a doc-only role in ZODB right now.
Nothing imports it.  The only thing that did try to import it was in
BTrees/__init__.py, but that import is gone now.  BTrees/Interfaces.py will
want to do better than this someday, but when that time comes it will
probably get its idea of interfaces from zope.interface.* instead.

> The file Support/zpkgtools/app.py contains a class called Application but
> it doesn't seem to be imported from anywhere else.

If Diez has a problem with that too, he can take it up with Fred <wink>.

> Of course, if you have objects of an unqualified class called
> "Application" stored in your ZODB..

Then you'll quickly learn to uninstall PythonCAD again <0.5 wink>.