runscript shouldn't swallow exceptions by default

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use a buggy script with runscript
2. Silence
3. (does anyone else have to fight the urge to type 'PROFIT!!' every time
they fill in one of these?)

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

An exception trace unless I've explicitly asked for a silent run.

What version of the product are you using? On what operating system?

n/a
Please provide any additional information below.

Original issue reported on code.google.com by andybak on 10 Mar 2009 at 10:57

[GoogleCodeExporter]

I agree, I've always hated having to type --traceback everytime, I can't think 
of a
reason why anyone would not want to know why a script failed. The only people 
running
these scripts are developers and administrators.

Original comment by e.willha...@gmail.com on 15 Mar 2009 at 10:30

• Changed state: Accepted

[GoogleCodeExporter]

I've committed a patch to my git repository of django-extensions which solves 
this
issue and adds one of the things on my wish-list for runscript.

It became a quite sizable patch, changing the flow of the code (sounds almost
philosophical :) substantially. 

Please take a look at it and comment on it:

http://github.com/trbs/django-extensions/commit/8c8c8d6e3f92e901bcfbf1e478fd0519
1355648c

Original comment by v.oostv...@gmail.com on 1 Apr 2009 at 8:32

• Changed state: Started

[GoogleCodeExporter]

Looks good! I'll do a similar thing to dumpscript to get some of that funky 
error
message going.

Original comment by e.willha...@gmail.com on 1 Apr 2009 at 8:47

[GoogleCodeExporter]

Sorry had to go out for diner and forgot to mention here what 'my-wish-list' 
thing was :)

The point was that i want runscript to tell when it didn't find a script called 
NAME. 

Original comment by v.oostv...@gmail.com on 1 Apr 2009 at 9:17

[GoogleCodeExporter]

patch is pushed into django-extensions at github

Original comment by v.oostv...@gmail.com on 16 Apr 2009 at 10:47

• Changed state: Fixed