Skip to main content

Parser like ConfigParser but for updating configuration files

Project description

Cirrus CI ReadTheDocs Coveralls PyPI-Server

ConfigUpdater

The sole purpose of ConfigUpdater is to easily update an INI config file with no changes to the original file except the intended ones. This means comments, the ordering of sections and key/value-pairs as wells as their cases are kept as in the original file. Thus ConfigUpdater provides complementary functionality to Python’s ConfigParser which is primarily meant for reading config files and writing new ones.

Features

The key differences to ConfigParser are:

  • minimal invasive changes in the update configuration file,

  • proper handling of comments,

  • only a single config file can be updated at a time,

  • empty lines in values are not valid,

  • the original case of sections and keys are kept,

  • control over the position of a new section/key

Following features are deliberately not implemented:

  • interpolation of values,

  • propagation of parameters from the default section,

  • conversions of values,

  • passing key/value-pairs with default argument,

  • non-strict mode allowing duplicate sections and keys.

Usage

First install the package with:

pip install configupdater

Now we can simply do:

from configupdater import ConfigUpdater

updater = ConfigUpdater()
updater.read('setup.cfg')

which would read the file setup.cfg that is found in many projects.

To change the value of an existing key we can simply do:

updater['metadata']['author'].value = "Alan Turing"

At any point we can print the current state of the configuration file with:

print(updater)

To update the read-in file just call updater.update_file() or updater.write('filename') to write the changed configuration file to another destination. Before actually writing, ConfigUpdater will automatically check that the updated configuration file is still valid by parsing it with the help of ConfigParser.

Many of ConfigParser’s methods still exists and it’s best to look them up in the module reference. Let’s look at some examples.

Adding and removing options

Let’s say we have the following configuration in a string:

cfg = """
[metadata]
author = Ada Lovelace
summary = The Analytical Engine
"""

We can add an license option, i.e. a key/value pair, in the same way we would do with ConfigParser:

updater = ConfigUpdater()
updater.read_string(cfg)
updater['metadata']['license'] = 'MIT'

A simple print(updater) will give show you that the new option was appended to the end:

[metadata]
author = Ada Lovelace
summary = The Analytical Engine
license = MIT

Since the license is really important to us let’s say we want to add it before the summary and even add a short comment before it:

updater = ConfigUpdater()
updater.read_string(cfg)
(updater['metadata']['summary'].add_before
                               .comment("Ada would have loved MIT")
                               .option('license', 'MIT'))

which would result in:

[metadata]
author = Ada Lovelace
# Ada would have loved MIT
license = MIT
summary = Analytical Engine calculating the Bernoulli numbers

Using add_after would give the same result and looks like:

updater = ConfigUpdater()
updater.read_string(cfg)
(updater['metadata']['author'].add_after
                              .comment("Ada would have loved MIT")
                              .option('license', 'MIT'))

Let’s say we want to rename summary to the more common description:

updater = ConfigUpdater()
updater.read_string(cfg)
updater['metadata']['summary'].key = 'description'

If we wanted no summary at all, we could just do del updater['metadata']['summary'].

Adding and removing sections

Adding and remove sections just works like adding and removing options but on a higher level. Sticking to our Ada Lovelace example, let’s say we want to add a section options just before metadata with a comment and two new lines to separate it from metadata:

updater = ConfigUpdater()
updater.read_string(cfg)
(updater['metadata'].add_before
                    .comment("Some specific project options")
                    .section("options")
                    .space(2))

As expected, this results in:

# Some specific project options
[options]

[metadata]
author = Ada Lovelace
summary = The Analytical Engine

We could now fill the new section with options like we learnt before. If we wanted to rename an existing section we could do this with the help of the name attribute:

updater['metadata'].name = 'MetaData'

Sometimes it might be useful to inject a new section not in a programmatic way but more declarative. Let’s assume we have thus defined our new section in a multi-line string:

sphinx_sect_str = """
[build_sphinx]
source_dir = docs
build_dir = docs/_build
"""

With the help of two ConfigUpdater objects we can easily inject this section into our example:

sphinx = ConfigUpdater()
sphinx.read_string(sphinx_sect_str)
sphinx_sect = sphinx['build_sphinx']

updater = ConfigUpdater()
updater.read_string(cfg)

(updater['metadata'].add_after
                    .space()
                    .section(sphinx_sect))

This results in:

[metadata]
author = Ada Lovelace
summary = The Analytical Engine

[build_sphinx]
source_dir = docs
build_dir = docs/_build

For more examples on how the API of ConfigUpdater works it’s best to take a look into the unit tests and read the references.

Notes

ConfigUpdater is mainly developed for PyScaffold.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

ConfigUpdater-1.0.1.tar.gz (30.9 kB view details)

Uploaded Source

Built Distribution

ConfigUpdater-1.0.1-py2.py3-none-any.whl (13.8 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file ConfigUpdater-1.0.1.tar.gz.

File metadata

  • Download URL: ConfigUpdater-1.0.1.tar.gz
  • Upload date:
  • Size: 30.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.7.4

File hashes

Hashes for ConfigUpdater-1.0.1.tar.gz
Algorithm Hash digest
SHA256 b750d8bc64bd22fa928feb12686e1e7135ff867730b23812e60cbd87cbe1c547
MD5 6fb0e4371b22d9bb72efa79181000aac
BLAKE2b-256 ae775d3c17609475ecd93b1ad5df28791e0d6424e000877ac4085003b4e81b9e

See more details on using hashes here.

File details

Details for the file ConfigUpdater-1.0.1-py2.py3-none-any.whl.

File metadata

  • Download URL: ConfigUpdater-1.0.1-py2.py3-none-any.whl
  • Upload date:
  • Size: 13.8 kB
  • Tags: Python 2, Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.7.4

File hashes

Hashes for ConfigUpdater-1.0.1-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 d7931993a0d54e31e6c0721c65e484f8736bfdcf5b466d258d44becf64c8169e
MD5 37fcfafcb71c3f0ed0f59adc5b57d768
BLAKE2b-256 196bec35716e860911fc4b40771781ab00e49925cc63a0882b938a6fbf51adfd

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page