head 1.8; access; symbols pkgsrc-2023Q4:1.7.0.2 pkgsrc-2023Q4-base:1.7 pkgsrc-2023Q3:1.6.0.12 pkgsrc-2023Q3-base:1.6 pkgsrc-2023Q2:1.6.0.10 pkgsrc-2023Q2-base:1.6 pkgsrc-2023Q1:1.6.0.8 pkgsrc-2023Q1-base:1.6 pkgsrc-2022Q4:1.6.0.6 pkgsrc-2022Q4-base:1.6 pkgsrc-2022Q3:1.6.0.4 pkgsrc-2022Q3-base:1.6 pkgsrc-2022Q2:1.6.0.2 pkgsrc-2022Q2-base:1.6 pkgsrc-2022Q1:1.5.0.2 pkgsrc-2022Q1-base:1.5 pkgsrc-2021Q4:1.4.0.8 pkgsrc-2021Q4-base:1.4 pkgsrc-2021Q3:1.4.0.6 pkgsrc-2021Q3-base:1.4 pkgsrc-2021Q2:1.4.0.4 pkgsrc-2021Q2-base:1.4 pkgsrc-2021Q1:1.4.0.2 pkgsrc-2021Q1-base:1.4 pkgsrc-2020Q4:1.3.0.2 pkgsrc-2020Q4-base:1.3 pkgsrc-2020Q3:1.2.0.24 pkgsrc-2020Q3-base:1.2 pkgsrc-2020Q2:1.2.0.22 pkgsrc-2020Q2-base:1.2 pkgsrc-2020Q1:1.2.0.18 pkgsrc-2020Q1-base:1.2 pkgsrc-2019Q4:1.2.0.20 pkgsrc-2019Q4-base:1.2 pkgsrc-2019Q3:1.2.0.16 pkgsrc-2019Q3-base:1.2 pkgsrc-2019Q2:1.2.0.14 pkgsrc-2019Q2-base:1.2 pkgsrc-2019Q1:1.2.0.12 pkgsrc-2019Q1-base:1.2 pkgsrc-2018Q4:1.2.0.10 pkgsrc-2018Q4-base:1.2 pkgsrc-2018Q3:1.2.0.8 pkgsrc-2018Q3-base:1.2 pkgsrc-2018Q2:1.2.0.6 pkgsrc-2018Q2-base:1.2 pkgsrc-2018Q1:1.2.0.4 pkgsrc-2018Q1-base:1.2 pkgsrc-2017Q4:1.2.0.2 pkgsrc-2017Q4-base:1.2 pkgsrc-2017Q3:1.1.0.26 pkgsrc-2017Q3-base:1.1 pkgsrc-2017Q2:1.1.0.22 pkgsrc-2017Q2-base:1.1 pkgsrc-2017Q1:1.1.0.20 pkgsrc-2017Q1-base:1.1 pkgsrc-2016Q4:1.1.0.18 pkgsrc-2016Q4-base:1.1 pkgsrc-2016Q3:1.1.0.16 pkgsrc-2016Q3-base:1.1 pkgsrc-2016Q2:1.1.0.14 pkgsrc-2016Q2-base:1.1 pkgsrc-2016Q1:1.1.0.12 pkgsrc-2016Q1-base:1.1 pkgsrc-2015Q4:1.1.0.10 pkgsrc-2015Q4-base:1.1 pkgsrc-2015Q3:1.1.0.8 pkgsrc-2015Q3-base:1.1 pkgsrc-2015Q2:1.1.0.6 pkgsrc-2015Q2-base:1.1 pkgsrc-2015Q1:1.1.0.4 pkgsrc-2015Q1-base:1.1 pkgsrc-2014Q4:1.1.0.2 pkgsrc-2014Q4-base:1.1; locks; strict; comment @# @; 1.8 date 2024.01.08.19.56.14; author adam; state Exp; branches; next 1.7; commitid T97t5Ylv1GQeqGTE; 1.7 date 2023.10.28.19.57.16; author wiz; state Exp; branches; next 1.6; commitid jP8MYROLWZ3yJqKE; 1.6 date 2022.04.30.11.11.01; author wiz; state Exp; branches; next 1.5; commitid XMz9gKO7y2xNndCD; 1.5 date 2022.01.07.17.04.31; author adam; state Exp; branches; next 1.4; commitid twrgxj21zasWXInD; 1.4 date 2021.02.07.15.42.49; author adam; state Exp; branches; next 1.3; commitid eJ8nUgidwqcMfNGC; 1.3 date 2020.09.30.07.01.52; author adam; state Exp; branches; next 1.2; commitid JgcbhqLm3UL6y2qC; 1.2 date 2017.10.07.11.18.28; author adam; state Exp; branches; next 1.1; commitid WZFwg7hVDMytY6aA; 1.1 date 2014.12.06.16.20.26; author rodent; state Exp; branches; next ; commitid EYszMenPW2lRWZ0y; desc @@ 1.8 log @py-structlog: updated to 24.1.0 24.1.0 Fixed - The lazy logger proxy returned by `structlog.get_logger()` now returns its initial values when asked for context. When asked for context before binding for the first time, it returned an empty dictionary in 23.3.0. - The displayed level name when using `structlog.stdlib.BoundLogger.exception()` is `"error"` instead of `"exception"`. Fixes regression in 23.3.0. - Don't ignore the `width` argument of `RichTracebackFormatter`. 23.3.0 Added - The colorful development logger is now even more configurable! Choose freely your colors and the order of the key-value pairs! Implement your own formatters for certain keys! Implementing the output on top of the new columns API has changed the default very slightly, but shouldn't be noticeable. - Async log methods (those starting with an `a`) now also support the collection of callsite information using `structlog.processors.CallsiteParameterAdder`. Changed - `structlog.stdlib.recreate_defaults()` now also adds `structlog.stdlib.add_logger_name` to the processors. Check out the [updated screenshot](https://raw.githubusercontent.com/hynek/structlog/main/docs/_static/console_renderer.png)! Fixed - The return value from `get_logger()` (a `BoundLoggerLazyProxy`) now passes `isinstance`-checks against `structlog.typing.BindableLogger` on Python 3.12. - `structlog.threadlocal.tmp_bind()` now also works with `BoundLoggerLazyProxy` (in other words: before anything is bound to a bound logger). - stdlib: `ProcessorFormatter` can now be told to not render the log record message using `getMessage` and just `str(record.msg)` instead. - stdlib: `structlog.stdlib.BoundLogger.exception()`'s handling of`LogRecord.exc_info` is now set consistent with `logging`. @ text @@@comment $NetBSD: PLIST,v 1.7 2023/10/28 19:57:16 wiz Exp $ ${PYSITELIB}/${WHEEL_INFODIR}/METADATA ${PYSITELIB}/${WHEEL_INFODIR}/RECORD ${PYSITELIB}/${WHEEL_INFODIR}/WHEEL ${PYSITELIB}/${WHEEL_INFODIR}/licenses/LICENSE-APACHE ${PYSITELIB}/${WHEEL_INFODIR}/licenses/LICENSE-MIT ${PYSITELIB}/${WHEEL_INFODIR}/licenses/NOTICE ${PYSITELIB}/structlog/__init__.py ${PYSITELIB}/structlog/__init__.pyc ${PYSITELIB}/structlog/__init__.pyo ${PYSITELIB}/structlog/_base.py ${PYSITELIB}/structlog/_base.pyc ${PYSITELIB}/structlog/_base.pyo ${PYSITELIB}/structlog/_config.py ${PYSITELIB}/structlog/_config.pyc ${PYSITELIB}/structlog/_config.pyo ${PYSITELIB}/structlog/_frames.py ${PYSITELIB}/structlog/_frames.pyc ${PYSITELIB}/structlog/_frames.pyo ${PYSITELIB}/structlog/_generic.py ${PYSITELIB}/structlog/_generic.pyc ${PYSITELIB}/structlog/_generic.pyo ${PYSITELIB}/structlog/_greenlets.py ${PYSITELIB}/structlog/_greenlets.pyc ${PYSITELIB}/structlog/_greenlets.pyo ${PYSITELIB}/structlog/_log_levels.py ${PYSITELIB}/structlog/_log_levels.pyc ${PYSITELIB}/structlog/_log_levels.pyo ${PYSITELIB}/structlog/_native.py ${PYSITELIB}/structlog/_native.pyc ${PYSITELIB}/structlog/_native.pyo ${PYSITELIB}/structlog/_output.py ${PYSITELIB}/structlog/_output.pyc ${PYSITELIB}/structlog/_output.pyo ${PYSITELIB}/structlog/_utils.py ${PYSITELIB}/structlog/_utils.pyc ${PYSITELIB}/structlog/_utils.pyo ${PYSITELIB}/structlog/contextvars.py ${PYSITELIB}/structlog/contextvars.pyc ${PYSITELIB}/structlog/contextvars.pyo ${PYSITELIB}/structlog/dev.py ${PYSITELIB}/structlog/dev.pyc ${PYSITELIB}/structlog/dev.pyo ${PYSITELIB}/structlog/exceptions.py ${PYSITELIB}/structlog/exceptions.pyc ${PYSITELIB}/structlog/exceptions.pyo ${PYSITELIB}/structlog/processors.py ${PYSITELIB}/structlog/processors.pyc ${PYSITELIB}/structlog/processors.pyo ${PYSITELIB}/structlog/py.typed ${PYSITELIB}/structlog/stdlib.py ${PYSITELIB}/structlog/stdlib.pyc ${PYSITELIB}/structlog/stdlib.pyo ${PYSITELIB}/structlog/testing.py ${PYSITELIB}/structlog/testing.pyc ${PYSITELIB}/structlog/testing.pyo ${PYSITELIB}/structlog/threadlocal.py ${PYSITELIB}/structlog/threadlocal.pyc ${PYSITELIB}/structlog/threadlocal.pyo ${PYSITELIB}/structlog/tracebacks.py ${PYSITELIB}/structlog/tracebacks.pyc ${PYSITELIB}/structlog/tracebacks.pyo ${PYSITELIB}/structlog/twisted.py ${PYSITELIB}/structlog/twisted.pyc ${PYSITELIB}/structlog/twisted.pyo ${PYSITELIB}/structlog/types.py ${PYSITELIB}/structlog/types.pyc ${PYSITELIB}/structlog/types.pyo ${PYSITELIB}/structlog/typing.py ${PYSITELIB}/structlog/typing.pyc ${PYSITELIB}/structlog/typing.pyo @ 1.7 log @python/wheel.mk: simplify a lot, and switch to 'installer' for installation This follows the recommended bootstrap method (flit_core, build, installer). However, installer installs different files than pip, so update PLISTs for all packages using wheel.mk and bump their PKGREVISIONs. @ text @d1 1 a1 4 @@comment $NetBSD$ ${PYSITELIB}/${WHEEL_INFODIR}/LICENSE ${PYSITELIB}/${WHEEL_INFODIR}/LICENSE.apache2 ${PYSITELIB}/${WHEEL_INFODIR}/LICENSE.mit d5 3 d29 6 a34 3 ${PYSITELIB}/structlog/_loggers.py ${PYSITELIB}/structlog/_loggers.pyc ${PYSITELIB}/structlog/_loggers.pyo d60 3 d69 3 @ 1.6 log @py-structlog: fix build by using wheel.mk Add a missing test dependency, add test status @ text @a1 1 ${PYSITELIB}/${WHEEL_INFODIR}/INSTALLER a6 1 ${PYSITELIB}/${WHEEL_INFODIR}/REQUESTED a7 1 ${PYSITELIB}/${WHEEL_INFODIR}/direct_url.json d10 1 d13 1 d16 1 d19 1 d22 1 d25 1 d28 1 d31 1 d34 1 d37 1 d40 1 d43 1 d46 1 d50 1 d53 1 d56 1 d59 1 d62 1 @ 1.5 log @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 `_ 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 `_. 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. @ text @d1 10 a10 5 @@comment $NetBSD: PLIST,v 1.4 2021/02/07 15:42:49 adam Exp $ ${PYSITELIB}/${EGG_INFODIR}/PKG-INFO ${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt ${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt ${PYSITELIB}/${EGG_INFODIR}/top_level.txt a12 1 ${PYSITELIB}/structlog/__init__.pyo a14 1 ${PYSITELIB}/structlog/_base.pyo a16 1 ${PYSITELIB}/structlog/_config.pyo a18 1 ${PYSITELIB}/structlog/_frames.pyo a20 1 ${PYSITELIB}/structlog/_generic.pyo a22 1 ${PYSITELIB}/structlog/_greenlets.pyo a24 1 ${PYSITELIB}/structlog/_log_levels.pyo a26 1 ${PYSITELIB}/structlog/_loggers.pyo a28 1 ${PYSITELIB}/structlog/_utils.pyo a30 1 ${PYSITELIB}/structlog/contextvars.pyo a32 1 ${PYSITELIB}/structlog/dev.pyo a34 1 ${PYSITELIB}/structlog/exceptions.pyo a36 1 ${PYSITELIB}/structlog/processors.pyo a39 1 ${PYSITELIB}/structlog/stdlib.pyo a41 1 ${PYSITELIB}/structlog/testing.pyo a43 1 ${PYSITELIB}/structlog/threadlocal.pyo a45 1 ${PYSITELIB}/structlog/twisted.pyo a47 1 ${PYSITELIB}/structlog/types.pyo @ 1.4 log @py-structlog: updated to 20.2.0 20.2.0 Backward-incompatible changes: - Python 2.7 and 3.5 aren't supported anymore. The package meta data should ensure that you keep getting 20.1.0 on those versions. - ``structlog`` is now fully type-annotated. This won't break your applications, but if you use Mypy, it will most likely break your CI. Check out the new chapter on typing for details. Deprecations: - Accessing the ``_context`` attribute of a bound logger is now deprecated. Please use the new ``structlog.get_context()``. Changes: - ``structlog`` has now type hints for all of its APIs! Since ``structlog`` is highly dynamic and configurable, this led to a few concessions like a specialized ``structlog.stdlib.get_logger()`` whose only difference to ``structlog.get_logger()`` is that it has the correct type hints. We consider them provisional for the time being – i.e. the backward compatibility does not apply to them in its full strength until we feel we got it right. Please feel free to provide feedback! - Added ``structlog.make_filtering_logger`` that can be used like ``configure(wrapper_class=make_filtering_bound_logger(logging.INFO))``. It creates a highly optimized bound logger whose inactive methods only consist of a ``return None``. This is now also the default logger. - As a complement, ``structlog.stdlib.add_log_level()`` can now additionally be imported as ``structlog.processors.add_log_level`` since it just adds the method name to the event dict. - ``structlog.processors.add_log_level()`` is now part of the default configuration. - ``structlog.stdlib.ProcessorFormatter`` no longer uses exceptions for control flow, allowing ``foreign_pre_chain`` processors to use ``sys.exc_info()`` to access the real exception. - Added ``structlog.BytesLogger`` to avoid unnecessary encoding round trips. Concretely this is useful with *orjson* which returns bytes. - The final processor now also may return bytes that are passed untouched to the wrapped logger. - ``structlog.get_context()`` allows you to retrieve the original context of a bound logger. - ``structlog.PrintLogger`` now supports ``copy.deepcopy()``. - Added ``structlog.testing.CapturingLogger`` for more unit testing goodness. - Added ``structlog.stdlib.AsyncBoundLogger`` that executes logging calls in a thread executor and therefore doesn't block. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.3 2020/09/30 07:01:52 adam Exp $ a4 2 ${PYSITELIB}/${EGG_INFODIR}/not-zip-safe ${PYSITELIB}/${EGG_INFODIR}/requires.txt @ 1.3 log @py-structlog: updated to 20.1.0 20.1.0 Deprecations: - This is the last version to support Python 2.7 (including PyPy) and 3.5. All following versions will only support Python 3.6 or later. Changes: - Added a new module ``structlog.contextvars`` that allows to have a global but context-local ``structlog`` context the same way as with ``structlog.threadlocal`` since 19.2.0. - Added a new module ``structlog.testing`` for first class testing support. The first entry is the context manager ``capture_logs()`` that allows to make assertions about structured log calls. - Added ``structlog.threadlocal.unbind_threadlocal()``. - The logger created by ``structlog.get_logger()`` is not detected as an abstract method anymore, when attached to an abstract base class. - ``colorama`` isn't initialized lazily on Windows anymore because it breaks rendering. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.2 2017/10/07 11:18:28 adam Exp $ d23 6 d47 1 d60 3 @ 1.2 log @py-structlog: update to 17.2.0 17.2.0: - ``structlog.stdlib.ProcessorFormatter`` now accepts *keep_exc_info* and *keep_stack_info* arguments to control what to do with this information on log records. Most likely you want them both to be ``False`` therefore it's the default. - ``structlog.stdlib.add_logger_name()`` now works in ``structlog.stdlib.ProcessorFormatter``'s ``foreign_pre_chain``. - Clear log record args in ``structlog.stdlib.ProcessorFormatter`` after rendering. This fix is for you if you tried to use it and got ``TypeError: not all arguments converted during string formatting`` exceptions. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.1 2014/12/06 16:20:26 rodent Exp $ d29 3 d44 3 @ 1.1 log @Import py27-structlog-0.4.2 as sysutils/py-structlog. structlog makes structured logging in Python easy by augmenting your existing logger. It allows you to split your log entries up into key/value pairs and build them incrementally without annoying boilerplate code. @ text @d1 1 a1 1 @@comment $NetBSD$ d5 2 a13 3 ${PYSITELIB}/structlog/_compat.py ${PYSITELIB}/structlog/_compat.pyc ${PYSITELIB}/structlog/_compat.pyo a16 3 ${PYSITELIB}/structlog/_exc.py ${PYSITELIB}/structlog/_exc.pyc ${PYSITELIB}/structlog/_exc.pyo d29 6 @