Log Message:
py-structlog: updated to 21.5.0

21.5.0 (2021-12-16)
-------------------
Changes:
- Added the ``structlog.processors.LogfmtRenderer`` processor to render log \ 
lines using the `logfmt <https://brandur.org/logfmt>`_ format.
- Added the ``structlog.stdlib.ExtraAdder`` processor that adds extra attributes \ 
of ``logging.LogRecord`` objects to the event dictionary.
  This processor can be used for adding data passed in the ``extra`` parameter \ 
of the ``logging`` module's log methods to the event dictionary.
- Added the ``structlog.processor.CallsiteParameterAdder`` processor that adds \ 
parameters of the callsite that an event dictionary orginated from to the event \ 
dictionary.
  This processor can be used to enrich events dictionaries with information such \ 
as the function name, line number and filename that an event dictionary \ 
orignated from.

21.4.0 (2021-11-25)
-------------------
Changes:
- Fixed import when running in optimized mode (``PYTHONOPTIMIZE=2`` or ``python \ 
-OO``).
- Added the ``structlog.threadlocal.bound_threadlocal`` and \ 
``structlog.contextvars.bound_contextvars`` decorator/context managers to \ 
temporarily bind key/value pairs to a thread-local and context-local context.

21.3.0 (2021-11-20)
-------------------
Backward-incompatible changes:
- ``structlog`` switched its packaging to `flit \ 
<https://flit.readthedocs.io/>`_.
  Users shouldn't notice a difference, but (re-)packagers might.

Changes:
- ``structlog.dev.ConsoleRenderer`` now has ``sort_keys`` boolean parameter that \ 
allows to disable the sorting of keys on output.
- ``structlog.processors.TimeStamper`` now works well with FreezeGun even when \ 
it gets applied before the loggers are configured.
- ``structlog.stdlib.AsyncBoundLogger`` now determines the running loop when \ 
logging, not on instantiation.
  That has a minor performance impact, but makes it more robust when loops \ 
change (e.g. ``aiohttp.web.run_app()``), or you want to use ``sync_bl`` *before* \ 
a loop has started.
- ``structlog.stdlib.ProcessorFormatter`` now has a *processors* argument that \ 
allows to define a processor chain to run over *all* log entries.

  Before running the chain, two additional keys are added to the event \ 
dictionary: ``_record`` and ``_from_structlog``.
  With them it's possible to extract information from ``logging.LogRecord``\s \ 
and differentiate between ``structlog`` and ``logging`` log entries while \ 
processing them.

  The old *processor* (singular) parameter is now deprecated, but no plans exist \ 
to remove it.