Nick Coghlan writes:
I wonder: should we start putting some of these process details for
the different phases in the release PEPs themselves? Larry sent a good
summary to python-committers for 3.5 a while back, but they'd be
easier to find in the PEPs, and it would also make it clear
On 14 July 2015 at 17:19, Stephen J. Turnbull step...@xemacs.org wrote:
Nick Coghlan writes:
I wonder: should we start putting some of these process details for
the different phases in the release PEPs themselves? Larry sent a good
summary to python-committers for 3.5 a while back, but
On 14 July 2015 at 12:28, Robert Collins robe...@robertcollins.net wrote:
On 14 July 2015 at 14:25, R. David Murray rdmur...@bitdance.com wrote:
On Tue, 14 Jul 2015 14:01:25 +1200, Robert Collins
robe...@robertcollins.net wrote:
So unittest.mock regressed during 3.5, and I found out when I
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
On 14 July 2015 at 14:25, R. David Murray rdmur...@bitdance.com wrote:
On Tue, 14 Jul 2015 14:01:25 +1200, Robert Collins
robe...@robertcollins.net 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
On Tue, 14 Jul 2015 14:01:25 +1200, Robert Collins robe...@robertcollins.net
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
