Environment for embedded python actions
Posted: Thu Sep 01, 2011 12:42 am
Can you give us some hints on the environment that embedded python code runs in? I gather its runs in some separate host of its own (sort of like a plugin?). How does this host differ from a plugin host, environment-wise?
I can see that the "indigo" module is pre-imported. Is there any way to control the import path? I'd like my actions to import my support harness (the one I stick into my plugins), but it's not obvious how to do this.
Can embedded Python code leave data behind - such as setting globals or defining functions and classes? Or does the host clean up after each script fragment runs?
What happens (or is supposed to happen) when an embedded Python fragment uses pluginProps? Whose properties are we getting and setting?
(Will the questions ever stop? )
Cheers
-- perry
I can see that the "indigo" module is pre-imported. Is there any way to control the import path? I'd like my actions to import my support harness (the one I stick into my plugins), but it's not obvious how to do this.
Can embedded Python code leave data behind - such as setting globals or defining functions and classes? Or does the host clean up after each script fragment runs?
What happens (or is supposed to happen) when an embedded Python fragment uses pluginProps? Whose properties are we getting and setting?
(Will the questions ever stop? )
Cheers
-- perry