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 michael.foord
Recipients Amit Saha, Amit.Saha, The Compiler, kushal.das, michael.foord, rbcollins, vstinner
Date 2016-02-23.10:06:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1456221976.18.0.327688558625.issue26323@psf.upfronthosting.co.za>
In-reply-to
Content
There have been persistent calls for an "assert_called" method over the lifetime of mock. In the past I've rejected them because you can easily get it by asserting the call count is non-zero and I want to avoid the proliferation of a thousand assert methods. The demand is certainly consistent, so it would seem that people feel there is a use case.
History
Date User Action Args
2016-02-23 10:06:16michael.foordsetrecipients: + michael.foord, vstinner, rbcollins, kushal.das, Amit.Saha, The Compiler, Amit Saha
2016-02-23 10:06:16michael.foordsetmessageid: <1456221976.18.0.327688558625.issue26323@psf.upfronthosting.co.za>
2016-02-23 10:06:16michael.foordlinkissue26323 messages
2016-02-23 10:06:15michael.foordcreate