-
Notifications
You must be signed in to change notification settings - Fork 162
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
fix compatibility with pytest ^8 #776
Changes from 1 commit
d53c129
14c40ae
321fde3
4b93d5a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
# Always adjust install_requires in setup.cfg and pytest-min-requirements.txt | ||
# when changing runtime dependencies | ||
pytest >= 7.0.0,<8 | ||
pytest >= 7.0.0, !=8.0.0rc1, !=8.0.0rc2 | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,7 +14,7 @@ packaging==23.2 | |
pluggy==1.3.0 | ||
py==1.11.0 | ||
Pygments==2.16.1 | ||
pytest==7.0.0 | ||
pytest==8.0.0 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The intention of the I think we should continue to support pytest 7 for at least a short period of time, in order to allow users to migrate pytest independently from pytest-asyncio. |
||
requests==2.31.0 | ||
sortedcontainers==2.4.0 | ||
tomli==2.0.1 | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
# Always adjust install_requires in setup.cfg and requirements.txt | ||
# when changing minimum version dependencies | ||
pytest[testing] == 7.0.0 | ||
pytest[testing] == 8.0.0 |
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.
I ran your patch successfully against pytest-8.0.0rc1 and pytest-8.0.0rc2. This means there's not reason to exclude them in the compatible versions. It's more likely that #764 reduced the number of issues with the collection changes in pytest.
More importantly, we should try to keep the upper version bound at all costs, both in
requirements.txt
and especially insetup.py
. Otherwise we assume that pytest-asyncio is compatible with potentially breaking changes in pytest 9.