Interactive shell terminates whenever an exception is raised

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run googlecl interactively
2. Execute something which raises an Exception, for instance, "blogger --qwerty"

What is the expected output? What do you see instead?

Expected to show an error stack. Currently when the exception is raised the 
GoogleCL shell is terminated.

What version of the product are you using? On what operating system? What
version of gdata-python-client (aka python-gdata)?

Revision 301

Please provide any additional information below.

Attached a patch proposal to solve it.

Original issue reported on code.google.com by ferranb@gmail.com on 27 Jun 2010 at 11:11

Attachments:

• shell_exception_capture.patch

[GoogleCodeExporter]

I don't know if showing the error stack trace to a user of GoogleCL is how this 
should be handled.  If anything, the exception should be handled internally and 
present a reasonable error message to the user via stderr.

Another thought is to have a --debug switch allowing to view stack traces, etc. 
 Owners, what are your thoughts?

Original comment by ericvw on 28 Jun 2010 at 1:32

[GoogleCodeExporter]

The patch's target is to avoid crashing the shell and solve annoying shell 
re-runs.

I agree that is desirable to give better feedback and to hide the stack-trace 
when something wrong happens but that involves a deeper analysis on the way of 
handle feedback on options, arguments and exceptions.

Waiting for owners feedback...

Original comment by ferranb@gmail.com on 28 Jun 2010 at 8:47

[GoogleCodeExporter]

Ultimately, the stack trace will be hidden from the user. But since we're still 
in beta, it's valuable for the user to easily report the entire stack trace to 
us.

This also helps the windows exe in issue 54. Well timed. :)

Original comment by tom.h.mi...@gmail.com on 30 Jun 2010 at 3:13

• Changed state: Accepted

[GoogleCodeExporter]

This issue was closed by revision r313.

Original comment by tom.h.mi...@gmail.com on 30 Jun 2010 at 3:28

• Changed state: Fixed