Support for pyproject.toml as config file format

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:

[tool.bandit]
targets = ["src"]
skips = ["B101", "B110"]

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:

• https://github.com/python/mypy/issues/5205
• https://github.com/pytest-dev/pytest/issues/1556
• https://github.com/nedbat/coveragepy/issues/664

[moon-bits]

@ericwb I’m sorry to say that: But this is getting ridiculous.

There is a pending PR https://github.com/PyCQA/bandit/pull/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.

[derek-miller]

Any update here? Can you either merge the PR or reject it? Nearly all other linting related packages have support for pyproject.toml at this point and a shame users still need to use multiple configuration files for a solved problem.