PEP8-tification is an intrusive task. In my experience it often causes conflicts with active patches and feature branches. The task should be coordinated with all developers.

The autopep8 tool is a good tool to automate most of the boring tasks. It's not perfect but it does 95% of the job in a matter of seconds. https://pypi.python.org/pypi/autopep8

Once we have archived PEP8 compliance, flake8 and two additional plugins can ensure that Dogtag stays PEP8 conform:

- https://pypi.python.org/pypi/flake8
- https://pypi.python.org/pypi/flake8-import-order
- https://pypi.python.org/pypi/pep8-naming

attachment
pep8.patch

I have attached a patch which I generated with autopep8

   $ find base/ -name '*.py' | xargs autopep8 --diff --ignore E309 --aggressive

The auto-generated patch isn't perfect, but itaddresses most PEP8 violations. Some lines need manual improvements, too.

Moving to 'critical' so that this is addressed early for 10.3.

Pushed to master in 12badcabc1cd345256a4902f7b0583cf667ecd8d

Internal change

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1277

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.