On 14 July 2015 at 12:28, Robert Collins wrote:
> On 14 July 2015 at 14:25, R. David Murray wrote:
>> On Tue, 14 Jul 2015 14:01:25 +1200, Robert Collins
>> wrote:
>>> So unittest.mock regressed during 3.5, and I found out when I released
>>> the mock backport.
>>>
>>> The regression is pretty s
On Tue, 14 Jul 2015 14:01:25 +1200, Robert Collins
wrote:
> So unittest.mock regressed during 3.5, and I found out when I released
> the mock backport.
>
> The regression is pretty shallow - I've applied the fix to 3.6, its a
> one-liner and comes with a patch.
>
> Whats the process for getting
On 14 July 2015 at 14:25, R. David Murray wrote:
> On Tue, 14 Jul 2015 14:01:25 +1200, Robert Collins
> wrote:
>> So unittest.mock regressed during 3.5, and I found out when I released
>> the mock backport.
>>
>> The regression is pretty shallow - I've applied the fix to 3.6, its a
>> one-liner
So unittest.mock regressed during 3.5, and I found out when I released
the mock backport.
The regression is pretty shallow - I've applied the fix to 3.6, its a
one-liner and comes with a patch.
Whats the process for getting this into 3.5? Its likely to affect a
lot of folk using mock (pretty much
