Skip to content
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

[BUG] Vulture doesn't report unused method under Prospector #598

Open
rpatterson opened this issue Feb 26, 2023 · 1 comment
Open

[BUG] Vulture doesn't report unused method under Prospector #598

rpatterson opened this issue Feb 26, 2023 · 1 comment

Comments

@rpatterson
Copy link

Describe the bug

Running Vulture directly reports unused method:

$ vulture ./src/foo/
src/foo/bar.py:##: unused method 'qux' (##% confidence)

But running it under Prospector reports nothing:

$ prospector ./src/foo/
Check Information
=================
         Started: ####-##-## ##:##:##.######
        Finished: ####-##-## ##:##:##.######
      Time Taken: #.## seconds
       Formatter: grouped
        Profiles: .prospector.yaml, full_pep8, doc_warnings, strictness_veryhigh, member_warnings
      Strictness: from profile
  Libraries Used: 
       Tools Run: bandit, dodgy, mccabe, mypy, profile-validator, pycodestyle, pydocstyle, pyflakes, pylint, vulture
  Messages Found: 0
 External Config: pylint: ./pyproject.toml

Environment:

  • OS: Docker python:3.11 image
  • Tool: pylint
  • Prospector version: v1.9.0
  • Python version: v3.11.2
@rpatterson
Copy link
Author

I'm guessing this is because Prospector hard codes the vulture checks to perform? Maybe it would be best to find someway to let Vulture define the list of checks it performs so that they're included in Prospector as Vulture changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant