All 15 Debugging & Profiling questions
More in Debugging & Profiling
How do assert statements work for debugging, and why should they NOT be relied upon for production input validation? How do you use Python's built-in 'warnings' module to surface deprecated or risky code paths during debugging? How would you use the 'faulthandler' module to diagnose a program that crashes with a segmentation fault, typically from a C extension? How do you use memory_profiler (or tracemalloc from the standard library) to identify a memory leak's source in a Python application? How do you use pdb's post-mortem debugging mode to inspect a program's state exactly at the point where an unhandled exception occurred? How would you profile memory allocations specifically (not just CPU time) to find which objects are consuming the most memory in a running process? How do you use conditional breakpoints in pdb to pause execution only when a specific condition is met, avoiding manually stepping through many unrelated iterations? How would you use line_profiler (a third-party tool) to get LINE-BY-LINE timing information within a specific function, more granular than cProfile's function-level data? How would you use py-spy (a sampling profiler) to profile a running Python process in PRODUCTION without restarting it or adding any code changes?
Advertisement
Back to results for “Debugging”
Python › Debugging & Profiling

How would you use the 'logging' module's exception logging (logger.exception()) INSIDE an except block to automatically capture the full traceback?

Advanced

Answer

logger.exception(message) is a convenience method equivalent to logger.error(message, exc_info=True) — it MUST be called from WITHIN an except block (where sys.exc_info() has current exception data), and automatically appends the full traceback to the log record, avoiding the need to manually call traceback.format_exc().
import logging
logger = logging.getLogger(__name__)

try:
    result = 1 / 0
except ZeroDivisionError:
    logger.exception("Failed to calculate result")  # automatically includes the full traceback
Real-world example Automatically logging complete diagnostic tracebacks for unexpected errors caught in a production service's exception handlers.

Common follow-ups: What happens if you accidentally call logger.exception() OUTSIDE of an active except block?

Logging
All 15 Debugging & Profiling questions