Can one of the admins verify this patch?

ok to test

• Is it mergable
• Did it pass the tests?
• N/A If it introduces new functionality in scripts/ is it tested?
  Check for code coverage.
• Is it well formatted? Look at pep8/pylint, cppcheck, and
  make doc output. Use autopep8 and astyle -A10 --max-code-length=80
  if needed.
• Is it documented in the Changelog?
• N/A Was spellcheck run on the source code and documentation after changes
  were made?

Great. Add a changelog entry and I'll merge this.

Thanks @chuckpr !

Hello @Echelon9,

Thank you for your enthusiasm in helping clean up the code base. This commit is from pull request #452 in response to issue #447. There is no need to chase down which commit where messiness crept in; we'd rather focus on improving the codebase from here on out.

I think I'm going to add make diff_pylint_report to the checklist to bring attention to this sort of thing.