Linter always uses /usr/local/bin/flake8 about sublimelinter-flake8

[sjahl]

I was able to resolve this by manually specifying the linter executable with the setting provided in #38, like so:

        "linters":
        {
            "flake8": {
                "executable": "/Users/username/.virtualenvs/myvirtualenv/bin/flake8"
            }
        }

Which I can do on a per-project bases (and works well enough for me). I still believe that there's a bug here -- that we can't rely on the executable at /usr/local/bin/flake8 to actually correspond to the version of python we have defined with @python.

Perhaps an easy solution is to call flake8 with something like python<version> -m flake8 as is recommended (for users with multiple python versions installed) in the Note here: https://flake8.readthedocs.io/en/latest/#using-flake8 ?

[posita]

@sjahl wrote:

I was able to resolve this by manually specifying the linter executable with the setting provided in #38, like so:

        "linters":
        {
            "flake8": {
                "executable": "/Users/username/.virtualenvs/myvirtualenv/bin/flake8"
            }
        }

This work-around does not work for me. (See SublimeLinter/SublimeLinter#573.)

Which I can do on a per-project bases (and works well enough for me).

Just curious, but does ${project} expansion work for you? (Meaning, would it work if you were to place the virtual env inside your project directory and then reference flake8 by, e.g., ${project}/.virtualenv/bin/flake8?)

[ptim]

@posita the ${project_path} expansion does work for me from my project-settings, though my flake8 extensions are not picked up...

{
  "SublimeLinter":
  {
    "linters":
    {
      "flake8": {
        "executable": "${project_path}/.direnv/python-3.6.1/bin/flake8",
      }
    }
  }
}

When SublimeLinter debug is true, I see on the console:

SublimeLinter: flake8: 0001_initial.py ['/Users/me/source/project/.direnv/python-3.6.1/bin/flake8', '--max-line-length=120', '--jobs=1', '--max-complexity=-1', '-'] 
SublimeLinter: flake8 output:
stdin:44:121: E501 line too long (176 > 120 characters)

I want this file (and all migrations) to be ignored via flake8-putty settings (which is working from the command line using the same flake8 binary).

[brianbruggeman]

Putting a comment in here so I can come back to the discussion later.

I very much would like to avoid using the ${project} dir for my virtual environments. That really goes against the ecosystem (i.e. WORKON folder / multiple projects). Seems like there's definitely something missing, though.

[groteworld]

This type of issue seems to be fixed with SL-flake8 3.0.0. Open if i'm mistaken