Non-secure execution environment

[rogeeff at gmail.com]

On Apr 17, 7:06 am, Aaron Brady <castiro... at gmail.com> wrote:
> On Apr 17, 1:47 am, roge... at gmail.com wrote:
>
>
>
> > Hi,
>
> > I am C++ guy for the most part and don't know much of Python, so,
> > please, bear with me if I am asking errrm..idiotic question.
>
> > Old rexec module provided kinda 'secure' execution environment. I am
> > not looking for security at this point. What I need an execution
> > environment which almost like rexec, but is non-secure.
> >   What I want is:
> >   separate global dictionary,
> >   separate list of imported modules,
> >   separate sys.path
> >   (optionaly) separate __builtins__
>
> > I might be able to get away without my own builtins, but the rest I
> > need.
>
> > If  it's any help, I plan to use it to execute embedded Python scripts
> > from C++.
>
> > Thanks,
>
> > Gennadiy
>
> It depends what you mean by secure environment.  One option is to
> create a subprocess, to just limit access your variables.  Another is
> to compile and examine their code yourself, and prohibit things like
> access to the file class, the os module, etc.

I actually need *non-secure* execution environment. I just want
several independent ones.

Gennadiy