From dd56009add5597f865bf0f353daa89f68038b332 Mon Sep 17 00:00:00 2001 From: disqualifier Date: Mon, 29 Jun 2026 01:10:25 -0400 Subject: [PATCH] docs: clarify resolution raises at initialize(), per-call resolution is swallowed the module docstring said resolution failures raise 'at initialize/call time', but per-call send-path resolution failures are swallowed with send failures (the documented intentional swallow). corrected to state resolution raises from initialize() at setup, while a per-call guild= that doesn't resolve falls back to stdlib like any send failure. Signed-off-by: disqualifier --- src/dpy_logger/dpy_logger.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/dpy_logger/dpy_logger.py b/src/dpy_logger/dpy_logger.py index be32230..40ba683 100644 --- a/src/dpy_logger/dpy_logger.py +++ b/src/dpy_logger/dpy_logger.py @@ -41,9 +41,10 @@ extending: this base has no feed/announcement method by design. a project that wants one subclasses DPYLogger and adds it, reusing _resolve. errors: resolution failures (unresolvable guild/channel, bad config) raise -ValueError at initialize/call time — a misconfigured logger should fail loudly. -per-call send failures do NOT propagate: they fall back to the stdlib logger so -a transient discord failure never breaks the caller's command. +ValueError from `initialize()` — a misconfigured logger should fail loudly at +setup. on a per-call send, resolution AND send failures do NOT propagate: they +fall back to the stdlib logger so a transient discord failure (or a per-call +`guild=` that doesn't resolve) never breaks the caller's command. """ import logging