From cf235b6f31c3c0d9cecd9bf9e52599b6ccb0112f Mon Sep 17 00:00:00 2001 From: Daniel Szoke Date: Mon, 14 Apr 2025 10:18:05 +0200 Subject: [PATCH] fix(debug): Do not consider parent loggers for debug logging This reverts commit 37930840dcefba96e7708b19e461013a919e83a5, which made the SDK consider parent loggers when determining if the Sentry SDK should log debug messages. However, we should not consider parent loggers, since we only want the SDK to log debug messages when configured to do so via `debug=True` (in `sentry_sdk.init`), the `SENTRY_DEBUG` environment variable, or via a specific logger configuration for `sentry_sdk.errors`. With 37930840dcefba96e7708b19e461013a919e83a5, a custom root logger configuration would also cause SDK logs to be emitted. The issue 37930840dcefba96e7708b19e461013a919e83a5 was meant to fix (#3944) appears to have been caused by user error, not a bug in the SDK. Fixes #4266 --- sentry_sdk/debug.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sentry_sdk/debug.py b/sentry_sdk/debug.py index f740d92dec..e4c686a3e8 100644 --- a/sentry_sdk/debug.py +++ b/sentry_sdk/debug.py @@ -19,7 +19,7 @@ def filter(self, record): def init_debug_support(): # type: () -> None - if not logger.hasHandlers(): + if not logger.handlers: configure_logger()