-
-
Notifications
You must be signed in to change notification settings - Fork 649
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
Bump default Pytest to 4.6 and add warning for future change to Pytest 5 #8648
Conversation
28e5ad7
to
37696b9
Compare
ed4eee1
to
66d22be
Compare
66d22be
to
4c56576
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huzzah!
Ugh, this still strikes:
Looks like we do need #8621. @jsirois does merging #8621 still sound like the right approach? |
4c56576
to
a8c4f88
Compare
- changed number of = signs - 3rdparty dep test now prints a DeprecationWarning that we can't silence for some reason
This broke coverage.
a8c4f88
to
e2472bb
Compare
Problem
We're using an old version of Pytest from 2018 and are two major releases behind. This means users are missing out on new features like Pytest 5.0 enabling
faulthandler
by default and that certain plugins won't work because Pytest is too outdated.However, Pytest 5.0 drops support for running tests with Python 2.
Solution
Set the default Pytest to 4.6.x, which is the last minor series to support Python 2. This brings nice benefits to users without being majorly breaking.
Then, we add a deprecation for users not specifying
--pytest-version
to ensure that they don't get bit by us switching to Pytest 5 in two major releases.Finally, we set our own internal Pytest to the newest release so that we get the newest and greatest, e.g. default
faulthandler
.Result
Users who have not specified
--pytest-version
will get this warning: