NEWS for lazr.config

2.2.3 (2021-01-26)

  • Fix tests with zope.interface >= 5.0.0.

  • Fix deprecation warning on Python >= 3.2. (LP: #1870199)

2.2.2 (2019-11-04)

  • Officially add support for Python 3.7 and 3.8. The test suite required some changes since the repr of datetime.timedelta objects changed in 3.7.

2.2.1 (2017-10-20)

  • Adjust versioning strategy to avoid importing pkg_resources, which is slow in large environments.

2.2 (2017-02-07)

  • Fix tox import failure related to https://github.com/tox-dev/tox/issues/453 (LP: #1662701)

  • Don’t catch ImportErrors that might occur when importing lazr.config._config from lazr/config/__init__.py. It’s unnecessary and masks legitimate ImportErrors of e.g. lazr.delegates.

  • setup.py: nose is not an install_requires, so move this dependency to tox.ini. (LP: #1649726)

  • tox.ini: Add the py36 environment and drop py32, py33. Ignore missing interpreters. Change to a temporary directory when running tox (to avoid the above tox bug). Invoke nose via -m instead of the mostly deprecated python setup.py approach.

2.1 (2015-01-05)

  • Always use old-style namespace package registration in lazr/__init__.py since the mere presence of this file subverts PEP 420 style namespace packages. (LP: #1407816)

  • For behavioral compatibility between Python 2 and 3, strict=False must be passed to the underlying RawConfigParser under Python 3. (LP: #1397779)

2.0.1 (2014-08-22)

  • Drop the use of distribute in favor of setuptools. (LP: #1359926)

  • Run the test suite with tox.

2.0 (2013-01-10)

  • Ported to Python 3.

  • Now more strict in its requirement of ASCII in config files.

  • Category names are now sorted by default.

1.1.3 (2009-08-25)

  • Fixed a build problem.

1.1.2 (2009-08-25)

  • Got rid of a sys.path hack.

1.1.1 (2009-03-24)

  • License clarification: only v3 of the LGPL is offered at this time, not subsequent versions.

  • Build is updated to support Sphinx docs and other small changes.

1.1 (2009-01-05)

  • Support for adding arbitrary sections in a configuration file, based on a .master section in the schema. The .master section allows admins to define configurations for an arbitrary number of processes. If the schema defines .master sections, then the conf file can contain sections that extend the .master section. These are like categories with templates except that the section names extending .master need not be named in the schema file. [Bug 310619]

  • ConfigSchema now provides an interface for constructing the schema from a string. [Bug 309859]

  • Added as_boolean() and as_log_level() type converters. [Bug 310782]

  • getByCategory() accepts a default argument. If the category is missing, the default argument is returned. If the category is missing and no default argument is given, a NoCategoryError is raised, as before. [Bug 309988]

1.0 (2008-12-19)

  • Initial release