DOC: Command to run flake8 on diff?
See original GitHub issueDescribe the issue linked to the documentation
In the Contributing code section of the Contributing page, it is stated that:
- Make sure that your PR does not add PEP8 violations. On a Unix-like system, you can run
make flake8-diff
.flake8 path_to_file
, would work for any system, but please avoid reformatting parts of the file that your pull request doesn’t change, as it distracts from code review.
I’ve never been able to run the make flake8-diff
command on MacOS. Does it require to install the flake8-diff Python package? The documentation of flake8 states that one can use the following command:
$ git diff -u | flake8 --diff
which works for me.
So I’m maybe asking a dumb question but what are the core devs using currently?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Full Listing of Options and Their Descriptions - Flake8
Show a description of how to use Flake8 and its options. Command-line usage: flake8 --help flake8 -h. This can not be specified in...
Read more >flake8 Documentation - Read the Docs
To install Flake8, open an interactive shell and run: ... Values set at the command line have highest priority, then those in the...
Read more >Support for flake8 --diff mode · Issue #2372 · dense-analysis/ale
Coming from having used Syntastic for a short while, I have it configured to lint python files using flake8 roughly as follows: git...
Read more >flake8 behaves differently when run from within a bash script
flake8 behaves differently when run from within a bash script · Can you show the result of type -a flake8 from the command...
Read more >Check code changes with flake8 before committing
On Linux or MacOS the command would be: ... The pre-commit hook is running flake8 against the current working copy, which contains the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I agree we shouldn’t recommend using it for windows users, but it doesn’t mean we shouldn’t have it for our own sake. We could have it but not recommend it. Although I kinda find it somewhat deeply problematic or ironic that for a lot of our contributing guides it’s not what we actually do. I guess we don’t have the bandwidth to do it, but it’d be nice to have a contributing guide for everybody, and one for people with a POSIX system.
Note that makefile is not cross-plaform, so we shouldn’t recommend using makefile in the contribution docs IMO. A lot of potential contributors are on windows.