Hi i'm not sure exactly whats being asked here. zope on linux doesn't include its own python interpreter. you can choose which one executes zope and its external methods by specifing the interpreter binary in the start.py. its quite possible that your installing third party modules into the distros python in /usr/bin/python, in which case if zope's using /usr/local/bin/python you won't see them and you'll get import errors. if this is the case copying the third party modules into /usr/lib/python1.5/site-packages will solve the import errors, or moving the modules into the zope_dir/lib/python/ (or perhaps a subdirectory with an init) might do the trick. if you specifically want to run something through a custom python interp from zope you might need to use os.popen2 (or variant) in an external method, or setup sometype of interprocess communication via xml-rpc or an rdbms or shared file, etc. hope that helps kapil Gary Perez wrote:
Hi.
We've got Zope 2.2.2 installed on a Linux box. We want to be able to use the full-up python that's on the box instead of the python interpreter that comes with Zope for playing with External Methods.
Is there any way to circumvent Zope's python in this way?
If not, what's the easiest way to extend Zope to be able to use our non-Zope python?
Alternatively, we're plagued by import and attribute errors when accessing the External Methods. Will simply moving (or linking?) all the pieces (whatever.py, __init__.py, etc.) into a subdirectory of "Shared" fix the problem?
Thanks in advance for your help. -GMP
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )