On Aug 13, 3:31 pm, Scott <[EMAIL PROTECTED]> wrote:
> What I would like is the full stack trace of what went wrong on the
> server (i.e. the junk python usually dumps to the console when an
> exception occurs). I don't care which side I see the dump on (client
> or server), but I need to see the
Scott wrote:
I'm debugging an xmlrpc client/server application. Often when an
exception occurs in the server, I receive only a very short error
message on the client. For example:
xmlrpclib.Fault: :">
Presumably this is because xmlrpclib on the server is catching the
exception, and only se
