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 carljm
Recipients berker.peksag, brett.cannon, carljm, kushal.das, michael.foord, rbcollins
Date 2015-07-21.16:32:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As a frequent and long-time user of mock, the `assert_*` methods being on the mock object itself has always struck me as an unfortunate wart on an otherwise great library. The change to raise `AssertionError` on `assert_*` and `assret_*` feels like piling an ugly band-aid on top of the wart. I'd love to see Robert's suggested solution of moving the assertion helpers to standalone functions.
Date User Action Args
2015-07-21 16:32:31carljmsetrecipients: + carljm, brett.cannon, rbcollins, michael.foord, berker.peksag, kushal.das
2015-07-21 16:32:31carljmsetmessageid: <>
2015-07-21 16:32:31carljmlinkissue24651 messages
2015-07-21 16:32:31carljmcreate