Open okainov opened 3 years ago
Would it make more sense to use pyproject.toml for this effort as part of modernization? See #550 which is awaiting some publish.
@asears yes and no :) From one side I'm all for supporting different formats, if it makes some folks happy, why not, more is not less. From the other side, in our projects we do use setup.cfg
with a lot of different tools and plugins and even if we would like to migrate to something (and we probably are not really into that for now), it wouldn't be so trivial and fast. And so far Bandit is the only tool from our set which doesn't support setup.cfg
as-is. So as a user I would love to see this implemented.
@asears Both my thumbs up go for this feature request - we only use setup.cfg
files at present as our code base has NOT been modernized and I don't think it will, because it simply works as it is and we have hundreds of python project only with setup.cfg
files...
Should be refused as won't fix due to PEP-621
Is your feature request related to a problem? Please describe.
I'd like to use single
setup.cfg
file for many different linters/plugins/style checkers. Currently bandit requires to have special config for it and is not able to readsetup.cfg
.Describe the solution you'd like
setup.cfg
(which is not YAML but more like INI-like format)Example:
Describe alternatives you've considered Separating configs which works, but clutters the workspace with files
Additional context Basically the same as https://github.com/PyCQA/bandit/issues/212 (which was probably closed by mistake)