@encthenet@flyovercountry.social
Post #2971423
2026-05-14 06:45 UTC
@glyph@mastodon.social
Nope, I want print_exc. Otherwise I'd have to do
except Exception as e:
And use orint_exceptilon.
print_stack would only help me find where I was being called from, not what the error was. Still useful but not what I was going for.
Replies (1)
-
@glyph@mastodon.social 2026-05-14 18:23
@encthenet@flyovercountry.social ah, I was reading “no clue where it’s being called from” as a bit more load-bearing to the problem here. I was incorrectly assuming that any sensible call site would have its own exception reporting and so the issue you were looking for was more “wait why isn’t the existing except: around this showing me what I need to know” rather than “what was the exception”