[TIP] removing attributes and dictionary keys using mock.patch

Michael Foord michael at voidspace.org.uk
Mon Dec 8 03:47:58 PST 2014


On 06/12/14 11:44, Chris Withers wrote:
> On 05/12/2014 18:34, Chris Withers wrote:
>>
>>> On 5 Dec 2014, at 18:19, Michael Foord <michael at voidspace.org.uk> 
>>> wrote:
>>>
>>
>>> I don't have any objection if the api can be clean and the 
>>> implementation isn't horrible.
>>
>> Do you have a preference for a marker object (like testfixtures uses) 
>> or a keyword param (such as delete=True)?
>>
>> A whole separate set of decorators/context managers/etc seems like 
>> overkill, so I hope that's not your preference ;-)
>
> Couple of process questions:
>
> - Is https://code.google.com/p/mock/ the right repo to develop against?

Nope. Python trunk is correct.
>
> - What's mock's release cycle?
>

Unknown. :-(

> - How go changes to Mock make their way into the Mock included in 
> Python 3?
>

It's going the other way  now. Or at least it should be. Primary 
development is in Python, with changes backported.

Michael

> cheers,
>
> Chris
>
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python




More information about the testing-in-python mailing list