collective.normalize_buildout 0.1

Features

normalize_buildout by default will replace the given config file in place. It has a command line option for not changing the file and only reporting via exit code if the file is not normalized. This can easily be integrated in check tools or ci tools.

The script understands the special meaning of some sections and keys:

• buildout section is always the first

• versions section is always the last

• recipe key is always first

• eggs, and zcml values get sorted.

• keys of sources entries get sorted, values get indented so that branch settings are all on the same column.

Comments above sections and above keys get shuffled together with key or section. You can document why you need to pin a specific version of a package and after normalization, the comment is still above the right version specifier. - Can be bullet points

Installation

You can install the package with pip or zc.buildout.

PIP:

$ pip install collective.normalize_buildout

Buildout:

[buildout]

 ...
 [extras]
 recipe = zc.recipe.egg
 eggs =
     collective.normalize_buildout

and then running “bin/buildout”

Contribute

• Issue Tracker: https://github.com/collective/collective.normalize_buildout/issues

• Source Code: https://github.com/collective/collective.normalize_buildout