-
-
Notifications
You must be signed in to change notification settings - Fork 710
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
Use pyproject.toml
for configuration?
#5725
Comments
Disclaimer: I'm not an expert I have a soft opinion towards moving all config. See below for a bit of research
https://www.python.org/dev/peps/pep-0518/
|
Flake8 does not, and has no plans, to support pyproject.toml: PyCQA/flake8#234 (unfortunately, that thread was migrated from GitLab and is very difficult to follow). Anyhow, Anthony has been very clear that Flake8 has no plans to support pyproject.toml now or in the future 🤷 |
I'd be in favor of moving things to a For what it's worth, Anthony is also against it for |
Makes sense. I agree that yaml is a better format for pre-commit. FWIW, I personally prefer |
In #5720 @ian-r-rose and @gjoseph92 brought up switching some (maybe all?) of our various tool configuration (e.g.
pytest
) fromsetup.cfg
to apyproject.toml
file. Some projects, e.g.pytest
, explicitly recommend against using asetup.cfg
file in favor of other configuration files likepyproject.toml
https://docs.pytest.org/en/6.2.x/customize.html#setup-cfg. I'm not familiar withpyproject.toml
so can't speak to various pros and cons -- opening up an issue to see if there's interest in usingpyproject.toml
The text was updated successfully, but these errors were encountered: