Python SDK Exception Hooks That Still Raise

sys.excepthook and threading.excepthook are process-wide. A library that replaces them will surprise every other dependency and can hide SystemExit or KeyboardInterrupt if it is careless. Instrument the methods you document.

Catch at the boundary, emit the probe, and raise the same exception with the original traceback. from None is the wrong tool here. You want the chain preserved.

Exception type, stable code, message with secrets stripped, stack, interpreter version, OS, and package version. Not os.environ. Not the full request. Not a pickle of the frame locals.

Locals are where tokens sit. If you ever snapshot variables, allow-list names like status_code and endpoint. Default to no locals.

If the SDK is imported by a web worker, input() will hang the worker. Gate the question 'What were you trying to do?' on an explicit CLI mode and a TTY. Everyone else gets a silent probe.

Exit status still comes from the CLI, not from the library. Map your exception types to the documented codes and let main() call sys.exit.

A week of ConnectionError messages will not tell you whether the quickstart URL is wrong. The code plus the one sentence will. Draft the issue with both, and let a person send it.

When the same code dominates, fix the sample or the default timeout. Do not wait for someone to paste a traceback into Discord.