setup.cfg: are linters/tools applicable to having configurations moved in?

[tony]

I use most of these utilities on my personal projects and have everything in setup.cfg. It would take more input than just me to justify/check on moving to setup.cfg, but it would clean up the root directory significantly.

Applicable?

• docformatter
• pytest
• flake8
• yapf
• isort
• autopep8
• unify

For any of the above, any chance of workflows breaking?

[agjohnson]

I'd be interested in this change. We have a number of repositories that we'd like to copy our autolinting to, but maintaining many copies of these files would be a headache.

The biggest win for us would be having prospector pick up on some of these files too, so our rules matches our auto-lint and lint steps.

If you have an example of this, we'd definitely me interested in a PR!

[tony]

@agjohnson

Greetings. I have a lot on my plate at the moment.

As a preliminary, let me show you my setup.cfg I use on my projects (Switched some names around)

[flake8]
inline-quotes = single
max-line-length = 100
max-complexity = 10
exclude = .git,
          __pycache__,
          readthedocs/static,
          my/node_modules

[tool:pytest]
DJANGO_SETTINGS_MODULE=readthedocs.settings.test
addopts=--ignore my/node_modules/ --ignore other/node_modules/

[isort]
combine_as_imports= true
default_section = THIRDPARTY
include_trailing_comma = true
multi_line_output = 3
known_django = django
known_pytest = pytest,py
known_docutils = docutils
known_first_party = readthedocs
sections = FUTURE,STDLIB,PYTEST,DJANGO,DOCUTILS,THIRDPARTY,FIRSTPARTY,LOCALFOLDER
line_length = 79
not_skip = __init__.py

[mypy]
show_column_numbers = True
show_error_context = True
ignore_missing_imports = True
follow_imports = skip
incremental = True
check_untyped_defs = True
warn_unused_ignores = True

The biggest win for us would be having prospector pick up on some of these files too, so our rules matches our auto-lint and lint steps.

It's my first time hearing about it. Careful about pulling it in as a dependency, it's GPLv2.

I will follow up on this ASAP. I have to square away some things on my end first

[stsewd]

We have the common repo now, is this issue still relevant?

[tony]

@stsewd I think it's good to close. I'm going to go ahead and do that now.