Skip to content
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

merge pytest.ini into setup.cfg #356

Merged
merged 4 commits into from
Jan 17, 2017
Merged

Conversation

renefritze
Copy link
Member

IIRC we held off on this due to
restricting ourselves to py.test >= 2.7.
This should be fine now woth py.test
already at 2.9.

IIRC we held off on this due to
restricting ourselves to py.test >= 2.7.
This should be fine now woth py.test
already at 2.9.
@renefritze renefritze added the infrastructure Buildsystem, packages and CI label Jan 15, 2017
@renefritze renefritze self-assigned this Jan 15, 2017
@renefritze
Copy link
Member Author

I forgot the actual reason was: pytest-dev/pytest#567
If we constrain pytest to >= 3.0 we can use [tool:pytest] in setup.cfg and be absolutely safe. I see no reason not to do that and will do that and merge tommorow afternoon unless someone objects first.

@renefritze renefritze merged commit 05a375d into master Jan 17, 2017
@renefritze renefritze deleted the merge_pytestini_into_setup branch January 17, 2017 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Buildsystem, packages and CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants