Providing full interaction with the run time

[Dale Strickland-Clark]

We have a system we're developing which runs as a server. It has an xml-rpc
interface which I've extended to provide some debugging facilities. This
has already proved very useful and will continue to be so as the system is
prepared for live deployment.

The debugging interface attempts to emulate the Python interactive shell.
You type expressions, you get an answer. You type statements, they get
executed.

The problem is these two types of input are handled differently by Python.
You don't seem to be able to pass statements (which includes assignments)
and expressions through the same calls.

There are three keywords that support this type of function: EXEC, EVAL and
COMPILE. We can ignore EXEC for this because it doesn't support saving and
restoring a local environment and EVAL can do it better.

When you COMPILE code for EVAL, you have to say what sort of statement it
is. You can't pass an assignment as an expression:
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "<>", line 1
a=1
^
SyntaxError: invalid syntax

However, changing option 'eval' to 'single' is OK for statements:

But if I use 'single', I can't get expression results because the stupid
function prints them on the console.
None

I can use the 'eval' option but that doesn't take assignments, remember?
1

The compile function also supports an 'exec' parameter in place of 'eval' or
'single' but this throws away expression results so that's no help.

At the moment, I'm making a crude attempt to distinguish between statements
and expressions but it's easily fooled.

So the question is: how does my debug interface (which operates over RPC)
decide which type of COMPILE it wants?

Or am I going about this all wrong?

(I don't need warnings about the obvious security implications of this
interface.)

Thanks

 

[Fredrik Lundh]

We have a system we're developing which runs as a server. It has an xml-rpc
interface which I've extended to provide some debugging facilities. This
has already proved very useful and will continue to be so as the system is
prepared for live deployment.

The debugging interface attempts to emulate the Python interactive shell.
You type expressions, you get an answer. You type statements, they get
executed.

The problem is these two types of input are handled differently by Python.
You don't seem to be able to pass statements (which includes assignments)
and expressions through the same calls.

There are three keywords that support this type of function: EXEC, EVAL and
COMPILE. We can ignore EXEC for this because it doesn't support saving and
restoring a local environment and EVAL can do it better.

huh? both exec and eval take optional execution contexts:

http://effbot.org/pyref/eval.htm
http://effbot.org/pyref/exec.htm

Or am I going about this all wrong?

yes, you're trying to reinvent the "code" module (and badly, it seems
;-). see the library reference to details, this page for some examples:

http://www.effbot.org/librarybook/code.htm

</F>

 

[Dale Strickland-Clark]

Thanks for the info. I didn't know about that module. I'll take a look.