[PythonCAD] Re: PythonCAD.pth and Interfaces.py

[ahaas at airmail.net]

>
> Hey Art,
>
>     We're running into trouble when running PythonCAD in conjunction
> with the ZODB BTrees. Both are doing naughty things <wink>.

Oooooo, naughtiness.

> BTrees tries importing an Interface module, and PythonCAD inserts itself
> into the PYTHONPATH via a .pth file -- and it has a top-level Interfaces
> package. This leads to nuclear meltdowns inside BTrees -- sometimes as
> far deep as inside Zope's guts -- because the Interface it's expecting
> isn't the Interface it's finding.

> Can this be fixed? Is adding bits to the global pythonpath really
> necessary? If anything, it burdens every other application in the system
> to run and look for modules in yet another directory, and leads to
> problems like this. If the .pth file is indeed essential, than at least
> protect the modules contained in the top-level package by a nice
> uniquish name -- like PythonCAD :-)

I'd thought that the way the modules are handled within PythonCAD wouldn't
conflict with other packages, but I guess that's not the case. Putting the
files into a 'PythonCAD' directory shouldn't be a problem (I think).

I'm hoping to make the next release at the end of this month, so I'll try
and get reorganize things so that the modules are in a safer directory.

Art