path to the flake8 linter is invalid

[swajime]

Hi, I am using VSCode with git bash. I have scripts that set up all the environment before launching VSCode, including activating a venv. When I open a python file in VSCode, I get an error that flake8 is not installed. I tried these settings:
Before running VSCode, I see VIRTUAL_ENV is /c/Users/MyName/venv_311

    "python.linting.flake8Path": "${env:VIRTUAL_ENV}/Scripts/flake8.exe" <-- preferred
    "python.linting.flake8Path": "${env:VIRTUAL_ENV}\\Scripts\\flake8.exe"
    "python.linting.flake8Path": "\"${env:VIRTUAL_ENV}/Scripts/flake8.exe\""
    "python.linting.flake8Path": "\"${env:VIRTUAL_ENV}\\Scripts\\flake8.exe\""
    "python.linting.flake8Path": "/c/Users/MyName/venv_311/Scripts/flake8.exe"
    "python.linting.flake8Path": "C:\\Users\\MyName\\venv_311\\Scripts\\flake8.exe"

This was not an issue last year. VSCode with Python became unavailable at my work for 6+ months. Now I have installed version 1.79.1 and have the issue ever since.

[brettcannon]

We don't officially support git bash, so it could play into that. I also don't think we support using ${env:VIRTUAL_ENV} in these settings (we fixed that a while back which might be the change over the last 6 months).

Have you tried our flake8 extension which ships with flake8 in-box?

[swajime]

Thanks,

In our environment we are not allowed to install plugins unless they are approved by a lengthy process. :-(
Is there no way to hack a fix in the local environment? I may be reduced to running from the command line only, and disabling the linters in VSCode.

Thanks,

John

[brettcannon]

You could write a Python script to auto-generate/update your .vscode/settings.json to put in the absolute path to your flake8 installation.

[swajime]

I have tried putting the absolute path in the settings. That is not working. I get the error mentioned in my original post.

…

On Wed, Aug 2, 2023, 4:15 PM Brett Cannon ***@***.***> wrote: You could write a Python script to auto-generate/update your .vscode/settings.json to put in the absolute path to your flake8 installation. — Reply to this email directly, view it on GitHub <#21737 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWWMHUTLCTECL5ZY2DLDF3XTKYPPANCNFSM6AAAAAA3BRXWBE> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[brettcannon]

If it's an absolute path for git bash then that would explain the issue.

I will warn you that we will be dropping our integrated flake8 support in our October release in favour of our flake8 extension. You might want to consider switching to something like a task to run flake8 on your behalf if you can't get your company to approve of you installing the flake8 extension (or use our Python extension template to create your own extension; had people wrap Pylint in under 2 hours with it).