-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Release 6.0.0rc1 #7459
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
Release 6.0.0rc1 #7459
Conversation
17e7f44
to
200d139
Compare
Deprecations | ||
------------ | ||
|
||
- `#6981 <https://github.com/pytest-dev/pytest/issues/6981>`_: Deprecate the ``pytest.collect`` module as it's just aliases into ``pytest``. |
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.
There is a known regression with this already: #6981 (comment)
(IIRC it does not happen with #6803)
Is #7362 ("Change pytest deprecation warnings into errors for 6.0 release") needed for this? |
I think so yes, this way release testers can try removing the warnings and reporting any problems. 👍 |
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.
f3277ae
to
0990cf8
Compare
0990cf8
to
b22d466
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.
Unfortunately I will make the release manually for now, given that this is really a problem with the tests and not with the code, and will fix the tests shortly in a separate PR. |
Also cleaned up the parametrized list using `pytest.param` to assign ids and removed some redundant cases. Follow up to pytest-dev#7459
@nicoddemus looks like the github release notes got missed: https://github.com/pytest-dev/pytest/releases/tag/6.0.0rc1 I assume this is related to the manual release? |
Ahh right, indeed it is, thanks for the heads up. Given that this is a prerelease I'm willing to leave it at that for now, unless someone really complains about it. 😁 |
alrighty sounds good to me! |
As discussed in #7447.