I need to stop my program when an exception is raised in Python. How do I implement this?
-
How do you want your program to stop?PEZ– PEZ2009-01-13 13:23:47 +00:00Commented Jan 13, 2009 at 13:23
-
1@Gortok: Thanks for adding [plzsendthecodez] tag. That made my day!S.Lott– S.Lott2009-01-13 13:40:20 +00:00Commented Jan 13, 2009 at 13:40
-
1If we were in C++ land, I would think that you're looking for the equivalent of "catch throw" in GDB. How ever, in Python the exception carries a backtrace telling you exactly where it's thrown from. Is this not enough?user3458– user34582009-01-13 15:03:33 +00:00Commented Jan 13, 2009 at 15:03
Add a comment
|
5 Answers
import sys
try:
print("stuff")
except:
sys.exit(1) # exiting with a non zero value is better for returning from an error
5 Comments
Deestan
sys.exit(1) would be more appropriate.
Loïc Wolff
@bruno desthuilliers Well, it's pretty obvious. All he asks was the script exiting when an exception occurs.
kramer65
@Deestan - Why is
sys.exit(1) more appropriate..?Deestan
@kramer65: A program exit code of
0 means "finished without errors". Since the sys.exit call appears to be caused by an error, it should yield a program exit code that is not 0. 1 is just a suggestion.
bruno desthuilliers
@LoïcWolff: There's nothing to do for the script to exit when an unhandled exception occurs. That's just the default behaviour - and at least it's a much saner behaviour since 1/ it prints a useful error message including the full traceback and 2/ returns with the appropriate (non zero) exit code.
You can stop catching the exception, or - if you need to catch it (to do some custom handling), you can re-raise:
try:
doSomeEvilThing()
except Exception, e:
handleException(e)
raise
Note that typing raise without passing an exception object causes the original traceback to be preserved. Typically it is much better than raise e.
Of course - you can also explicitly call
import sys
sys.exit(exitCodeYouFindAppropriate)
This causes SystemExit exception to be raised, and (unless you catch it somewhere) terminates your application with specified exit code.
1 Comment
Tobias Kienzler
As mentioned in this answer you can however use
sys.exc_info() to obtain enough information for a preserved re-raise if some processing is requiredIf you don't handle an exception, it will propagate up the call stack up to the interpreter, which will then display a traceback and exit. IOW : you don't have to do anything to make your script exit when an exception happens.
answered Jan 13, 2009 at 19:52
bruno desthuilliers
78.3k6 gold badges103 silver badges129 bronze badges
1 Comment
tbrlpld
This is the only real answer to the unspecific question. All other answers seems to make some implicit assumptions about that the author meant. Since we are talking Python, we should keep it as explicit as possible 😉😅
import sys
try:
import feedparser
except:
print "Error: Cannot import feedparser.\n"
sys.exit(1)
Here we're exiting with a status code of 1. It is usually also helpful to output an error message, write to a log, and clean up.
2 Comments
bruno desthuilliers
an unhandled exception WILL output with a (much more useful) error message (and the full traceback too) AND exit with non-zero status. Your above code snippet is an anti-pattern.
cowbert
It really depends on what the exception is being raised for. Remember that the higher level pattern is EAFP. So it's entirely possible that exception handling is being used to generate user feedback, and that user may only care about a sane error message and could do better without a trace. You can use
logging.exception to write the traceback to the log, present the user with meaningful feedback and then bail without reraising the exception.As far as I know, if an exception is not caught by your script, it will be interrupted.
Comments
