-
-
Notifications
You must be signed in to change notification settings - Fork 607
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
Support for pyproject.toml as config file format #550
Comments
Note, there is a PR in progress: #401 |
Thanks for pointing it out, I only searched the issues. Since it just extends the yaml config (that I wasn't even aware of), it should handle the example I proposed and much more, so it would close this issue satisfactorily. |
@ericwb I'm sorry to say that: But this is getting ridiculous. There is a pending PR #401 since October 2018, and you waste the time of the poor guy that still maintains the branch to keep it free from merge conflicts. Just merge it and please don't block it unnecessarily. We wait since 2 years for that feature that has been already implemented. |
Any update here? Can you either merge the PR or reject it? Nearly all other linting related packages have support for |
Seriously... please? :) |
Thanks a lot! Can you please publish a new release so that users can actually use it? |
Like others, I agree that it would be really great if a new release was on PyPI so that the Python community can benefit from the work that @orsinium and the other contributors/maintainers have done. |
Same here, given the age of the last release and the number of updates pending I think a new version should already be out. |
I did the PR 4 Hacktoberfest's ago, since then I have changed 3 cities, 2 countries, and 4 jobs, built a house, created 50+ small projects. So, be patient and just don't make expectations about the release date 😉 |
Ok, I guess I'll focus on building a house too and come back later 😉 |
…gs.json Bandit will soon support configuration via pyproject.toml but a version supporting this has not yet been released. See PyCQA/bandit#550
PEP 518 specifies a config format that can be exploited by dev tools through designated sections, given their pyPI domain. The toml format is very basic and should allow a simple 1 to 1 mapping of the existing config, since it is more on the minimal side. Given the following
.bandit
file:[bandit] targets: src skips: B101,B110
Its section in a pyproject.toml would look like this:
The sole gain of supporting this would be to reduce the amount of additional config files needed for using bandit in a python project that uses PEP 518 in some way from 1 to 0.
Discussions on other tools regarding the same issue:
The text was updated successfully, but these errors were encountered: