-
-
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
Test Outcomes as BaseException - fix #580 #2490
Conversation
CHANGELOG.rst
Outdated
@@ -1361,6 +1361,11 @@ time or change existing behaviors in order to make them less surprising/more use | |||
Thanks Mathieu Agopian for the report and Ronny Pfannschmidt for the PR. | |||
|
|||
- fix issue 1029: transform errors when writing cache values into pytest-warnings | |||
2.8.1 | |||
----------------------------- |
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.
Why are you adding an entry for 2.8.1
?
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 re-based the code - this one will go away
changelog/580.feature
Outdated
@@ -0,0 +1 @@ | |||
make pytest.fail/skip/xfail instances of BaseException |
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 think it would be nice to explain the change with some context to end-users, something like:
Exceptions raised by
pytest.fail
,pytest.skip
andpytest.xfail
now subclassBaseException
, making them harder to be caught unintentionally by normal code.
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.
Also if we will release a new major version, should we add this in a "backward incompatibility" section perhaps?
@nicoddemus i did realize that we may need to do a major release for this one due to changing the base-class of exposed types |
26ec52f
to
9c4a1d4
Compare
30d42de
to
c81380d
Compare
260545e
to
693bb32
Compare
693bb32
to
06a4933
Compare
As of pytest 3.2.0, the internal outcome class no longer inherits from Exception, rather from BaseException. This was reported in pytest-dev/pytest#580 and changed in pytest-dev/pytest#2490 Signed-off-by: Mike Fiedler <[email protected]>
As of pytest 3.2.0, the internal outcome class no longer inherits from Exception, rather from BaseException. This was reported in pytest-dev/pytest#580 and changed in pytest-dev/pytest#2490 Signed-off-by: Mike Fiedler <[email protected]>
Thanks for submitting a PR, your contribution is really appreciated!
Here's a quick checklist that should be present in PRs:
$issue_id.$type
for example (588.bug)removal
,feature
,bugfix
,vendor
,doc
ortrivial
bugfix
,vendor
,doc
ortrivial
fixes, targetmaster
; for removals or features targetfeatures
;