Bad idea to catch all exceptions in Python

by

Because it’s terribly nonspecific and it doesn’t enable you to do anything interesting with the exception. Moreover, if you’re catching every exception there could be loads of exceptions that are happening that you don’t even know are happening (which could cause your application to fail without you really knowing why). You should be able to predict (either through reading documentation or experimentation) specifically which exceptions you need to handle and how to handle them, but if you’re blindly suppressing all of them from the beginning you’ll never know.

So, by popular request, here’s an example. A programmer is writing Python code and she gets an IOError. Instead of investigating further, she decides to catch all exceptions:

def foo():
    try:
        f = open("file.txt")
        lines = f.readlines()
        return lines[0]
    except:
        return None

She doesn’t realize the issue in his ways: what if the file exists and is accessible, but it is empty? Then this code will raise an IndexError (since the list lines is empty). So she’ll spend hours wondering why she’s getting None back from this function when the file exists and isn’t locked without realizing something that would be obvious if she had been more specific in catching errors, which is that she’s accessing data that might not exist.

More Related Contents:

  1. Catch multiple exceptions in one line (except block)
  2. Is it a good practice to use try-except-else in Python?
  3. In Python, how does one catch warnings as if they were exceptions?
  4. How do I log a Python error with debug information?
  5. How to get exception message in Python properly
  6. Manually raising (throwing) an exception in Python
  7. I’m getting an IndentationError. How do I fix it?
  8. Why is “except: pass” a bad programming practice?
  9. Why does this iterative list-growing code give IndexError: list assignment index out of range?
  10. django MultiValueDictKeyError error, how do I deal with it
  11. How to retry after exception?
  12. Catching an exception while using a Python ‘with’ statement
  13. SyntaxError inconsistency in Python?
  14. Python: One Try Multiple Except
  15. UnicodeEncodeError: ‘ascii’ codec can’t encode character ‘\xe9’ – -when using urlib.request python3
  16. threading ignores KeyboardInterrupt exception
  17. How can I make silent exceptions louder in tkinter?
  18. Is there a way to prevent a SystemExit exception raised from sys.exit() from being caught?
  19. “Inner exception” (with traceback) in Python?
  20. Calling a hook function every time an Exception is raised
  21. hasattr() vs try-except block to deal with non-existent attributes
  22. One try block with multiple excepts
  23. python exception message capturing
  24. How to re-raise an exception in nested try/except blocks?
  25. Try/catch or validation for speed?
  26. Python FAQ: “How fast are exceptions?”
  27. Getting the exception value in Python
  28. Print an error message without printing a traceback and close the program when a condition is not met
  29. ‘sys.excepthook’ and threading
  30. Can Syntax Errors be handled?

Leave a Comment