Config-resolver

Latest version: v5.1.0

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

Scan your dependencies

Page 4 of 5

4.2.3

-------------

Fixes
~~~~~

* Unit tests fixed
* Added missing LICENSE file
* Log messages will now show the complete version string
* Auto-detect version number if none is specifiec in the ``[meta]`` section.
* Fix travis CI pipeline

4.2.2

-------------

Fixes
~~~~~

* Python 2/3 class-inheritance fixed.

4.2.1

-------------

Fixes
~~~~~

* Log message prefixes no longer added multiple times

4.2.0

-------------

Features added
~~~~~~~~~~~~~~

* GROUP and APP names are now included in the log messages.

4.1.0

-------------

Features added
~~~~~~~~~~~~~~

* XDG Basedir support

``config_resolver`` will now search in the folders/names defined in the `XDG
specification`_.

4.0.0

-------------

Features added
~~~~~~~~~~~~~~

* Config versioning support.

The config files can now have a section ``meta`` with the key ``version``.
The version is specified in dotted-notation with a major and minor number
(f.ex.: ``version=2.1``). Configuration instances take an optional
``version`` argument as well. If specified, config_resolver expects the
``meta.version`` to be there. It will raise a
``config_resolver.NoVersionError`` otherwise. Increments in the major number
signify an incompatible change. If the application expectes a different major
number than stored in the config file, it will raise a
``config_resolver.IncompatibleVersion`` exception. Differences in minor
numbers are only logged.

Improvments
~~~~~~~~~~~

* The ``mandatory`` argument **has been dropped**! It is now implicitly assumed
it the ``.get`` method does not specify a default value. Even though
"explicit is better than implicit", this better reflects the behaviour of the
core ``ConfigParser`` and is more intuitive.

* Legacy support of old environment variable names **has been dropped**!

* Python 3 support.

* When searching for a file on the current working directory, look for
``./.group/app/app.ini`` instead of simply ``./app.ini``. This solves a
conflict when two modules use config_resolver in the same application.

* Better logging.

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.