Dear EasyBuilders,
With the merge of [1] just now, automatic style checks on easyconfig
pull requests are now (finally) enabled.
This means that Travis is going to be picky about minor style issues in
contributed easyconfig files (trailing whitespace, no tabs, spaces
around '=' and after ',' and ':' (but not before), etc.).
Since easyconfig files are written in Python syntax, we adhere to the
PEP8 style guide [2],
with the exception of allowing lines to be 120 characters long (rather
than just 80).
You can check whether your easyconfig files adhere to the 'code' style
for easyconfig files using "eb --check-style".
Note that order & grouping of easyconfig parameter, which we also try to
keep consistent, is currently not checked yet.
There are plans to include that in --check-style and hence also the
automated style checks soon, see [3].
To be clear: this only applies to pull requests, not to easyconfig files
consumed by EasyBuild on the command line.
regards,
Kenneth
[1] https://github.com/hpcugent/easybuild-easyconfigs/pull/2506
[2] https://pep8.org/
[3] https://github.com/hpcugent/easybuild-framework/pull/2165
