I like solving problems. My dream job is to get paid to learn (and do cool stuff with that knowledge). When I'm not writing software, I'm making things out of wood, or baking something in the kitchen.
As someone who has inherited an... interesting... code base, I totally agree that flake8 is great. Another thing that we've been slowly trying to do as a team is clean up things as we go. E.g.: with every pull request, run and correct any flake8 warnings on functions that you touch. It's been slowly getting better.
Completely agree! I've done something exactly like how you describe. That method works great, especially for smaller teams! :)
The trouble is when it's a part of the build process it checks every file instead of just the areas around where you make changes. This is one of the nice things about having things like allow_failure in travis.yml along with similar options in other Continuous Integration services.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As someone who has inherited an... interesting... code base, I totally agree that flake8 is great. Another thing that we've been slowly trying to do as a team is clean up things as we go. E.g.: with every pull request, run and correct any flake8 warnings on functions that you touch. It's been slowly getting better.
Completely agree! I've done something exactly like how you describe. That method works great, especially for smaller teams! :)
The trouble is when it's a part of the build process it checks every file instead of just the areas around where you make changes. This is one of the nice things about having things like
allow_failureintravis.ymlalong with similar options in other Continuous Integration services.