Beispiel

Inject context variables into structlog loggers with merge_contextvars, scoped lifecycles, and asynchronous task isolation

sha256:6dec637d6343afe74048a5fc63a4dfef59e139a0fac7ba3e70880f3c05d653fa

Fall

Ziel

Inject context variables into structlog loggers with merge_contextvars, scoped lifecycles, and asynchronous task isolation HOW

Pakete

structlog 26.1.0

Umgebung

python

Erstellt

2026-08-17T19:44:47Z

Häufige Annahme

Calling bind_contextvars automatically propagates context variables to all structlog loggers without requiring merge_contextvars in the processor chain.

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

• Calling bind_contextvars has no effect on log output unless merge_contextvars is explicitly present in the processor chain, and bound logger fields override conflicting context variables.
• bound_contextvars restores previous context values upon block exit or exception while preserving unrelated keys.
• reset_contextvars with tokens returned by bind_contextvars restores previous variable bindings.
• unbind_contextvars deletes specified keys and clear_contextvars removes all context variables.
• get_merged_contextvars returns current contextvars merged with bound logger context without mutating either.
• Concurrent asyncio tasks inherit parent contextvars but mutate their context in complete isolation without leaking to siblings or the parent.

Dateien

• NOTES.md
• csx.json
• pyproject.toml
• requirements.lock
• requirements.txt
• test/contract.py

Quellartefakt herunterladen (tar.gz)

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• python 3.12 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9