Rick van Hattem

Given the current method we can effectively do that. As soon as we mark a plugin as flake8 compliant, travis won't allow failures anymore :)

To explain the current workings: - With every pull request and push to the Git repository Travis will automatically test everything - All modules (eg, plugins/*) are tested separately and...

Obviously the changes should be in style (i.e. whitespace) only and not change the meaning of the code. That's not something autopep8 or similar tools would do with the default...

Personally I have more faith in an auto formatter than a human when it comes to noticing the difference between the following: ``` x = 5 x = 5, x...

How about a hybrid solution? Add all of the packages to PyPI (perhaps with an eg-prefix for easy searching?) but create a separate Github repository where plugins can be added...

Instead of updating the site-packages manually in that manner it would probably be easier to use a virtualenv. Simply recreating the virtualenv removes all crud and the old environment can...

I've split the flake8 test so it tests every plugin separately which makes it easier to fix the plugins: https://travis-ci.org/WoLpH/EventGhost That way we could make it ignore all non-fixed plugins...

Whoops... that explains why I was getting weird errors :) Fixed now

Yes, exactly. It's simply a fully automated code quality test. Using these tests we can easily start converting plugins to adhere to the Python style guide and make sure they...

No, the other way around. I'm trying to connect to a firewalled server that's only reachable through the VPN. For convenience I want to setup a local reverse proxy so...