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 vstinner
Recipients berker.peksag, ericvw, grzgrzgrz3, mariocj89, michael.foord, rbcollins, vstinner
Date 2017-06-22.00:09:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I don't see what this buys over spec and autospec. I'd be inclined to close it without a compelling use case beyond what is already supported.

I proposed to Mario to open an issue since I like his API. Even if "sealing" mocks is unlikely to be the most common case, when you need it, I prefer his API over the specs thing which reminds me bad time with mox. I prefer the declarative Python-like API, rather than Mock(spec=["method2"], **{"method2.return_value": 1}).

But yeah, technically specs and sealing seems similar. It's just another way to describe a mock. Since I prefer sealing, I would like to allow users to choose between specs and sealing.
Date User Action Args
2017-06-22 00:09:25vstinnersetrecipients: + vstinner, rbcollins, ericvw, michael.foord, berker.peksag, grzgrzgrz3, mariocj89
2017-06-22 00:09:25vstinnersetmessageid: <>
2017-06-22 00:09:25vstinnerlinkissue30541 messages
2017-06-22 00:09:25vstinnercreate