CI and config file support

[7oi]

Config file support

I wanted this to run with django-jenkins flake8 task, but as it required cli options it was quite impossible. So I added config file parsing of the most common config files (setup.cfg, tox.ini, .flake8) to accommodate that need.

CI support

When running the django-jenkins flake8 task with flake-html it would render a report, but the format was off. It generates a report from the out stream from flake8 and the outstream was in the format {file} has issues: high: x medium: x for each file while I needed a pep8 report which goes: {file}:{error line}:{error column} {error code} {error text} for each error.

So I added the option to output a pep8 report.

Results

• Added benefit of reading config from a config file
• Running with django jenkins flake8 runner works and renders both html report and pep8 reports. The report itself is generated from the printed output, so in fact the only difference is that it outputs the compatible report to the cli rather than just how many issues each file has.
• Using the pep8 report changes is optional, as their operation is dependent on the values in config files/options. So it should work totally the same running it without using the htmlpep8 option or config value.

[lordmauve]

It looks like this change hasn't been tested on Python 3, which is why tests are failing.

Also, please bump the version to 0.4 rather than 0.3.1.

I might have some minor style comments when I did more into the code. In principle though this sounds like a good change.

[7oi]

Good catch. It seems that I imported the old python 2 ConfigParser rather than the imporved configparser (the lower-casing makes all the difference), which works with both python 2 and 3. I fixed that, trimmed away some unnecessary things and also bumped the version to 0.4.

[lordmauve]

Also, I notice a few lines are longer than 79 characters and therefore cause flake8 warnings. flake8-html should be flake8 clean, of course :)

[7oi]

Of course! It seemed that one line was longer than it should be. I fixed that. :)

[lordmauve]

I will release to PyPI when I can get in front of my laptop.

[lordmauve]

Released 0.4.0.