-
Notifications
You must be signed in to change notification settings - Fork 160
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
Add --config parameter to specify pyproject.toml path #352
Conversation
If you have a specific path to pyproject.toml in your project (e.g. not in the root), this allows `vulture` to read a config from that path.
@jendrikseipp I'm curious if you agree with this change? I found it useful in my project. If so, I can finish this up and do the checklist items. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! Yes, I like the suggested change.
Co-authored-by: Jendrik Seipp <jendrikseipp@gmail.com>
Co-authored-by: Jendrik Seipp <jendrikseipp@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I only have two minor nitpicks.
Co-authored-by: Jendrik Seipp <jendrikseipp@gmail.com>
Thanks! |
Description
For projects that have a pyproject.toml config in a directory other than the root, this allows
vulture
to accept--config path/to/pyproject.toml
(or-c path/to/pyproject.toml
).Related Issue
No issue created or found.
Checklist:
pre-commit run --all-files
to format and lint my code.