New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flake8 check does not respect projects python version #1212
Comments
yes, it is far from perfect. |
AFAIK PyFlakes relies on the Python itself is installed in to analyse the code (with Maybe this command can be tweaked to detect whether Flake8 is available in the project’s virtualenv, and use it if possible? |
I'd be more apt to remove the flake8 checking myself. |
That would be even better. |
It would be great to remove the Flake8 integration. In addition to the integration not working quite right, I also find it quite odd to see Flake8 end up in my production environments via Pipenv. |
So what would the desired outcome be to fix this ticket? Should |
Since it doesn't work properly and that doesn't seem to be an issue easily solved I'd also prefer removal, if at some point there will be a better solution that could be implemented if people agree on it, however, imo it shouldn't be left in a broken state. |
This is being worked on in #1394. |
pipenv check --style
appears to run the syntax check depending on its own python version instead of respecting the python version specified in the projects Pipfile.Describe your environment
$ python3 -V
:Python 3.5.3
$ pipenv --version
:pipenv, version 9.0.1
Expected result
No errors.
Actual result
Steps to replicate
pipenv check --style testfile.py
testfile.py
Pipfile
The text was updated successfully, but these errors were encountered: