1. Let's check the sanity of that eval's argument. :)
And also restrict the execution environment of that eval
to one that only contains the `subprocess' module,
but it seems to be of trivial use
as `subprocess' can do a lot of evil only by itself, :(
and the code below does not work as i expected!
The environment was not restricted at all! :(
restrict_env = {'subprocess':__import__('subprocess')}
eval('print(globals())', restrict_env)
The reason is in the docs,
`if the globals dictionary is present and lacks ‘__builtins__’,
the current globals are copied into globals
before expression is parsed'.
So, am i going to write a python sandbox?
No! At least not now! Stop here! Escaping is enough.
Let's assume it is enough. :)