[Zope] XXX-PythonMethods caveats?

[Tony McDonald]

At 9:55 pm -0500 14/3/00, Evan Simpson wrote:
>----- Original Message -----
>From: "Tony McDonald" <tony.mcdonald@ncl.ac.uk>
>[Unmistakable fierce-as-I-could-make-it warning omitted]
>>
>>  Of course, I then set
>>  do_XXX=1   :)
>
>Noooo!! <crash><snarl><rip> Aeeii!!! <rattle>

:(

>
>You might end up as a CPU server for arbitrary Python programs.  You might
>not.  LOOK OUT, IT'S BEHIND Y..<glurk>
>
>>  ps the icon for the XXX-PythonMethod object is way cool! :)
>
>They had to have *something* positive going for them :-)

<sigh>
Ok, I probably shouldn't use them then.
</sigh>

But (you knew there was going to be a but :). They are *so* useful.
E.g. I've got a XXXMethod that imports the following;
import os, sys, string, mimetypes, stat
import DocumentTemplate
from Acquisition import Implicit
from OFS.Image import File
from OFS.content_types import guess_content_type

setting do_XXX=0 gives me;

<!--
  Error type:  ImportError
  Error value: __import__ not found
  -->

Which is fair enough as the docs on the Zope site say import is 
controlled. Can you please be a bit more explicit and let me know 
*what* I can import? The Python code is a bit over my head...

<compromise>
Would you say that you could use a XXX PythonMethod to debug code 
that is going to become an External Method?
</compromise>

Thanks for the help Evan, it's much appreciated.
Tone.

------
Dr Tony McDonald,  FMCC, Networked Learning Environments Project 
http://nle.ncl.ac.uk/
The Medical School, Newcastle University Tel: +44 191 222 5888
Fingerprint: 3450 876D FA41 B926 D3DD  F8C3 F2D0 C3B9 8B38 18A2