This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xtreak
Recipients cjw296, guboi72, jekin000, jwdevel, mariocj89, michael.foord, rbcollins, xtreak
Date 2019-03-03.05:52:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551592368.11.0.0569182468029.issue26752@roundup.psfhosted.org>
In-reply-to
Content
eat_self is also a problem as mentioned and would help in solving issue27715 where self is not ignored. I tried a patch for issue27715 but that would require changing the output of some functions that take _eat_self as a parameter to return _eat_self since the functions themselves change the value. So some call sites need to be updated to receive actual value for _eat_self when the signature is created.

It's a hard issue and there are less tests in this area so it's even harder to figure out all the existing cases supported and if the solution is breaking existing code. Also the general repr during failure could be improved since it just says prints same call object for expected and actual with an assertion error making it more confusing (issue25312). 

I think there are currently 3-4 different variants of this issue in the tracker due to wrong signature that could be resolved if _call_matcher becomes more robust using correct signature.
History
Date User Action Args
2019-03-03 05:52:48xtreaksetrecipients: + xtreak, rbcollins, cjw296, michael.foord, jekin000, jwdevel, mariocj89, guboi72
2019-03-03 05:52:48xtreaksetmessageid: <1551592368.11.0.0569182468029.issue26752@roundup.psfhosted.org>
2019-03-03 05:52:48xtreaklinkissue26752 messages
2019-03-03 05:52:47xtreakcreate