Closed chagui closed 3 years ago
What is the benefit of moving pytest settings into pyproject.toml?
The benefit would be less configuration files in the project, and one place to lookup different configuration (project one or tools). However the pyproject.toml
is young and not adopted by every tool yet, and I know some project like it some other not so I am totally fine removing that part from the PR. It was more a suggestion rather than "we should do it this way"
The benefit would be less configuration files in the project, and one place to lookup different configuration (project one or tools). However the pyproject.toml is young and not adopted by every tool yet, and I know some project like it some other not so I am totally fine removing that part from the PR. It was more a suggestion rather than "we should do it this way"
I see. I don't have a strong preference for pytest.ini over pyproject.toml. If this gets us one less configuration file, and does not break anything, sure, why not.
I think if we do this, we should mention in contributor guide where we configure pytest, otherwise people might not see the config and add pytest.ini back.
Description
This pull-request propose to upgrade pytest to latest version (6.2.4) in order to:
I know some people are not fan of moving configuration to pyproject.toml and I would perfectly understand if you want to keep as is.
Checklist
changelog.rst
.pip install pre-commit && pre-commit install
), and ranblack
on my code.