-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add a default value to CallInfo.result #3560
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
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.
Great, thanks @alanbato!
I added some formatting to the CHANGELOG entry, after CI passes this is good to merge IMHO.
Thanks @nicoddemus! |
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.
This is a breaking change, it has to be reverted
Is |
@RonnyPfannschmidt is right, indeed it is used by:
Someone might be checking I will open a PR to revert this from |
As discussed in pytest-dev#3560, this should not go to master because this breaks the API. Reverts commits: 1a7dcd7 198e993
Opened #3562, thanks @RonnyPfannschmidt for catching my slip up |
AS per original issue callinfo needs a New state, something Like pre-call |
I see, because |
yes |
Agreed. @alanbato want to tackle that? |
Sure! Just to be sure though, do we want to include a new attribute that represents the different states? Something like |
@alanbato i beleive a
|
@RonnyPfannschmidt sounds good. I think the same check must be done for |
@nicoddemus that one is None at the class level |
Oh OK, thanks |
This was reverted in #3562 - what is the plan for it? |
well, i outlined the requirements for a correct fix above |
@alanbato |
New attempt in #4381. |
Fixes #3554
Any comments/questions welcome :)