Pin down flake8 version
See original GitHub issueDear authors of pre-commit,
I’ve been using this for quite some time in CI and everything worked nicely. However, today, new version of flake8 came out and as I install pre-commit
for every CI RUN new errors started to pop-out (W605 specifically).
Would it be possible to pin down the flake8 version in setup.py? And increase the version as versions of pre-commit-hooks
increase?
I’m willing to make the PR.
With regards Krystof
Issue Analytics
- State:
- Created 5 years ago
- Comments:22 (15 by maintainers)
Top Results From Across the Web
Flake8: Your Tool For Style Guide Enforcement — flake8 6.0.0 ...
To install Flake8, open an interactive shell and run: python<version> -m pip install flake8. If you want Flake8 to be installed for your...
Read more >flake8 2.4.0 not support pep8 1.6.2 version? - Stack Overflow
2 , now I can't run flake8 due to 2.4.0 not support >1.6 pep8 . Is there any way to downgrade pep8 to...
Read more >flake8-exact-pin - PyPI
A flake8 extension that checks for exact pins (e.q.: `foo==1.5.6`) in setup.py. ... You are forcing them to use a particular version that...
Read more >User Guide - pip documentation v22.3.1
In this case, your requirement file contains a pinned version of everything that was installed when pip freeze was run. Unix/macOS.
Read more >Modern Python Environments - dependency and workspace ...
Once you get through the pain of setting up a Python environment for a ... Lock files pin down (or lock) all dependency...
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
If you’d like to select a specific version, you can do that with:
that said, as stated above the plan is to (eventually) move the
flake8
hook out ofpre-commit-hooks
into a repository which updates with flake8 (maybe even flake8 itself now that I’m a maintainer). this will userev
for the version and will function withautoupdate