narrativetrace-structlog 0.1.1__tar.gz → 0.1.2__tar.gz

{narrativetrace_structlog-0.1.1 → narrativetrace_structlog-0.1.2}/.gitignore

@@ -23,3 +23,7 @@ build/
 # Local tooling state (contains credentials — never commit)
 
 # Local tooling state (holds host-absolute paths)
+
+# narrativetrace-pytest's default per-test artifact directory -- on by default, opt out with
+# NARRATIVETRACE_OUTPUT=false (see documentation/what-to-commit.md)
+narrative-traces/

{narrativetrace_structlog-0.1.1 → narrativetrace_structlog-0.1.2}/LICENSE

@@ -7,7 +7,7 @@ Parameters
 
 Licensor:             Empower Agile
 
-Licensed Work:        NarrativeTrace for Python (the narrativetrace PyPI distributions) version 0.1.1. The Licensed Work is (c) 2026 Empower Agile.
+Licensed Work:        NarrativeTrace for Python (the narrativetrace PyPI distributions) version 0.1.2. The Licensed Work is (c) 2026 Empower Agile.
 
 Additional Use Grant: You may make production use of the Licensed Work for any
                       purpose, including internal use and use in products and
@@ -18,7 +18,7 @@ Additional Use Grant: You may make production use of the Licensed Work for any
                       parties as a logging, tracing, or code-narrative product
                       or service.
 
-Change Date:          Four years from the date the Licensed Work is published. (2030-09-11 for this version)
+Change Date:          Four years from the date the Licensed Work is published. (2030-09-16 for this version)
 
 Change License:       Apache License, Version 2.0
 

{narrativetrace_structlog-0.1.1 → narrativetrace_structlog-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: narrativetrace-structlog
-Version: 0.1.1
+Version: 0.1.2
 Summary: structlog processor injecting narrativetrace correlation keys
 Project-URL: Homepage, https://github.com/narrativetrace/narrativetrace-python
 Project-URL: Source, https://github.com/narrativetrace/narrativetrace-python
@@ -10,8 +10,7 @@ License-File: LICENSE
 Classifier: Typing :: Typed
 Requires-Python: >=3.12
 Requires-Dist: narrativetrace
-Provides-Extra: structlog
-Requires-Dist: structlog>=24; extra == 'structlog'
+Requires-Dist: structlog>=24
 Description-Content-Type: text/markdown
 
 # narrativetrace-structlog

{narrativetrace_structlog-0.1.1 → narrativetrace_structlog-0.1.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "narrativetrace-structlog"
-version = "0.1.1"
+version = "0.1.2"
 description = "structlog processor injecting narrativetrace correlation keys"
 readme = "README.md"
 requires-python = ">=3.12"
@@ -10,21 +10,15 @@ license = "BUSL-1.1"
 license-files = ["LICENSE"]
 authors = [{ name = "narrativetrace contributors" }]
 classifiers = ["Typing :: Typed"]
-dependencies = ["narrativetrace"]
+dependencies = ["narrativetrace", "structlog>=24"]
 
 [project.urls]
 Homepage = "https://github.com/narrativetrace/narrativetrace-python"
 Source = "https://github.com/narrativetrace/narrativetrace-python"
 
-[project.optional-dependencies]
-structlog = ["structlog>=24"]
-
 [build-system]
 requires = ["hatchling"]
 build-backend = "hatchling.build"
 
 [tool.hatch.build.targets.wheel]
 packages = ["src/narrativetrace_structlog"]
-
-[dependency-groups]
-dev = ["structlog>=24"]

{narrativetrace_structlog-0.1.1 → narrativetrace_structlog-0.1.2}/src/narrativetrace_structlog/__init__.py

@@ -22,19 +22,26 @@ Usage::
 
 from __future__ import annotations
 
+from collections.abc import MutableMapping
 from typing import Any
 
 from narrativetrace import current_scope_keys
 
-__version__ = "0.1.1"
+__version__ = "0.1.2"
 
 __all__ = ["narrative_context_processor"]
 
 
 def narrative_context_processor(
-    _logger: Any, _method_name: str, event_dict: dict[str, Any]
-) -> dict[str, Any]:
-    """A structlog processor adding the current scope's correlation keys (without overwriting)."""
+    _logger: Any, _method_name: str, event_dict: MutableMapping[str, Any]
+) -> MutableMapping[str, Any]:
+    """A structlog processor adding the current scope's correlation keys (without overwriting).
+
+    Typed against ``MutableMapping``, not ``dict``: structlog's own ``Processor`` protocol takes
+    the broader type, so a narrower one here fails strict mypy the moment a caller feeds this
+    straight into ``structlog.configure(processors=[...])`` -- found running exactly that, this
+    guide's own documented usage example, under this repository's strict mypy gate.
+    """
     for key, value in current_scope_keys().items():
         event_dict.setdefault(key, value)
     return event_dict

{narrativetrace_structlog-0.1.1 → narrativetrace_structlog-0.1.2}/tests/test_processor.py

@@ -57,7 +57,12 @@ class TestProcessor:
         assert narrative_context_processor(None, "info", {"event": "hi"}) == {"event": "hi"}
 
     def test_emits_identical_keys_to_stdlib_filter(self) -> None:
-        """The structlog processor and the stdlib filter must produce the same key set."""
+        """The structlog processor and the stdlib filter must produce the same key set, with one
+        documented exception: the stdlib filter also always defaults `traceName`/`runName` to `""`
+        (2026-09-13 ruling) so a `%`-style format string referencing either never raises
+        `KeyError` on a record with no active trace/run -- structlog's event dict needs no such
+        protection, since a missing dict key is never a formatting crash the way an absent
+        LogRecord attribute is."""
         _enter_span()
         with request_log_scope({"httpMethod": "GET"}):
             processor_keys = set(narrative_context_processor(None, "info", {})) - {"event"}
@@ -67,4 +72,4 @@ class TestProcessor:
             base = set(logging.LogRecord("t", logging.INFO, __file__, 1, "m", None, None).__dict__)
             filter_keys = set(record.__dict__) - base
 
-        assert processor_keys == filter_keys
+        assert processor_keys == filter_keys - {"runName"}