Zconfig

Latest version: v4.1

Safety actively analyzes 638437 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 6

3.4.0

==================

Many changes have been made in the support for logging configurations:

- The log handler section types defined by the
``ZConfig.components.logger`` package support additional, optional
parameters:

``style``
Used to configure alternate format styles as found in the Python 3
standard library. Four ``style`` values are supported:
``classic`` (the default), ``format`` (equivalent to ``style='{'``
in Python 3), ``template`` (equivalent to ``style='$'``), and
``safe-template`` (similar to ``template``, but using the
``string.Template`` method ``safe_substitute`` method). A
best-effort implementation is provided for Python 2.

``arbitrary-fields``
A Boolean defauting to ``False`` for backward compatibility,
allows arbitrary replacement field names to be accepted in the
format string (regardless of the ``style`` setting). This
supports applications where log records are known to be generated
with additional string or numeric fields, at least for some
loggers. (An exception is still raised at format time if the
additional fields are not provided, unless the ``style`` value
``safe-template`` is used.)

- The ``logfile`` section type defined by the ``ZConfig.components.logger``
package supports the optional ``delay`` and ``encoding`` parameters.
These can only be used for regular files, not the special ``STDOUT``
and ``STDERR`` streams.

- More validation on the parameters to the ``logfile`` and
``email-notifier`` sections is performed early (at the construction of
the factory, rather than at creation of the ``logging`` handler).
This allows more checking of parameter combinations before any log
files are opened.

- The ``ZConfig.components.logger.handlers.log_format`` data type
function now supports formats that include numeric formatting for
``levelno``, and accept ``funcName`` as a valid log record field
(added in Python 2.6 and 3.1).

3.3.0

==================

- Drop support for Python 3.3.

- Add support for Python 3.7.

- Drop support for 'python setup.py test'. See `issue 38
<https://github.com/zopefoundation/ZConfig/issues/38>`_.

- Add support for ``example`` in ``section`` and ``multisection``, and
include those examples in generated documentation. See
https://github.com/zopefoundation/ZConfig/pull/5.

- Fix configuration loaders to decode byte data using UTF-8 instead of
the default encoding (usually ASCII). See `issue 37
<https://github.com/zopefoundation/ZConfig/issues/37>`_.

3.2.0

==================

- Drop support for Python 2.6 and 3.2 and add support for Python 3.6.

- Run tests with pypy and pypy3 as well.

- Host docs at https://zconfig.readthedocs.io

- BaseLoader is now an abstract class that cannot be instantiated.

- Allow ``nan``, ``inf`` and ``-inf`` values for floats in
configurations. See
https://github.com/zopefoundation/ZConfig/issues/16.

- Scripts ``zconfig`` (for schema validation) and
``zconfig_schema2html`` are ported to Python 3.

- A new ``ZConfig.sphinx`` `Sphinx extension
<https://zconfig.readthedocs.io/en/latest/documenting-components.html#documenting-components>`_
facilitates automatically documenting ZConfig components using their
description and examples in Sphinx documentation. See
https://github.com/zopefoundation/ZConfig/pull/25.

- Simplify internal schema processing of max and min occurrence
values. See https://github.com/zopefoundation/ZConfig/issues/15.

- Almost all uses of ``type`` as a parameter name have been replaced
with ``type_`` to avoid shadowing a builtin. These were typically
not public APIs and weren't expected to be called with keyword
arguments so there should not be any user-visible changes. See
https://github.com/zopefoundation/ZConfig/issues/17

3.1.0

==================

- Add ability to do variable substitution from environment variables using
$() syntax.

3.0.4

==================

- Added Python 3.4 support.

3.0.3

==================

- Added Python 3.2 support.

Page 2 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.