-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Unpin pytest #26625
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
Unpin pytest #26625
Conversation
Codecov Report
@@ Coverage Diff @@
## master #26625 +/- ##
==========================================
- Coverage 91.87% 91.87% -0.01%
==========================================
Files 174 174
Lines 50692 50692
==========================================
- Hits 46575 46571 -4
- Misses 4117 4121 +4
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #26625 +/- ##
==========================================
- Coverage 91.88% 91.87% -0.01%
==========================================
Files 174 174
Lines 50692 50692
==========================================
- Hits 46576 46572 -4
- Misses 4116 4120 +4
Continue to review full report at Codecov.
|
Interestingly I think there still might be an issue with the pytest release based on:
will take a further look tomorrow |
bumped up to latest pytest release which should fix this - CI running.. |
@jreback : How does it work when it comes to developer dependencies? Should we be bumping version requirements this high to be the latest version? |
doesn’t make sense to bump this - we try to move very slowly in things like thus |
Given that pandas tests will fail running with pytest version 4.6.0 and 4.6.1 doesn’t it make sense to enforce this in the dependencies? ( yes we could do this by keeping the current pin in place ). But keeping it pinned means nothing in CI will draw our attention to any future breaking pytest changes? Potentially making it harder to update further down the road. What do you think ? |
these are 3.5 builds only - pinning is ok to be honest could pin them to a much earlier version all other builds float to the latest |
Follow up from #26619. Since pytest have just done a point release for 4.6.1 we should be good to remove the pin.
pytest-dev/pytest#5358
cc @simonjayhawkins