You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interestingly adjusting the Pylama args in VSCode to include --vulture-min-confidence 80 doesn't stop pylama from working correctly but also doesn't change the output (i.e. I still have warnings with confidence under 80%).
The full command that is run during this is: ~/.virtualenvs/<project-name>/bin/python ~/.vscode-server/extensions/ms-python.python-2023.8.0/pythonFiles/linter.py -m pylama "--vulture-min-confidence 80" ./src/main/helpers.py
Edit: Adding in 2 arguments, --vulture-min-confidence and 80 appears to have done the trick, although this is still a work-around I'd prefer to avoid as it makes keeping settings consistent between projects and team members more difficult. (Nope, I can't reproduce this sadly)
Vulture option under
[tool.pylama.linter.vulture]
asmin_confidence
The following
pyproject.toml
that has themin-confidence
configuration option specified with hyphens as underscores:causes the following output/error when pylama is run:
Vulture option under
[tool.pylama.linter.vulture]
asmin-confidence
Running instead with with
min-confidence
as-is appears to show the correct output but is not shown in VSCode (not sure why):output:
Vulture option specified under
[tool.vulture]
asmin_confidence
Running under
[tool.vulture]
with underscores half works as above, producing output but not registering in VSCodeVulture option specified under
[tool.vulture]
asmin-confidence
Running under
[tool.vulture]
with hyphen produces an erroroutput:
I'm not sure if I'm doing something wrong or have missed some trick, any advice appreciated.
The text was updated successfully, but these errors were encountered: