-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Preparing release version 5.0.0 #5509
Conversation
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.
comment to `#5402 <https://github.com/pytest-dev/pytest/issues/5402>`__. | ||
|
||
|
||
- `#5412 <https://github.com/pytest-dev/pytest/issues/5412>`_: ``ExceptionInfo`` objects (returned by ``pytest.raises``) now have the same ``str`` representation as ``repr``, which |
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.
(not for this release, random thought)
I'm thinking of adding a "Changes" to incorporate changes like this one: it is not a removal, merely a change in behavior which can potentially break existing suites. Thoughts?
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.
yeah seems fair to split it out -- I use a separate "Updating" section for pre-commit's changelogs: https://github.com/pre-commit/pre-commit/blob/master/CHANGELOG.md#updating
@nicoddemus alright, this should be ready again :D |
Awesome, ship it! 😁 🎉 |
Don't forget to send the announcement email 😉 |
yep :) just did that! |
email? Weird still have not gotten it... |
No description provided.