Share your own username with Michael or I and we'll add you there.
Rob
On Mon, 29 Apr 2019, 09:55 Chris Withers, wrote:
> On 28/04/2019 22:21, Robert Collins wrote:
> > Thank you!
>
> Thank me when we get there ;-) Currently in Dec 2018 with a wonderful
> Py2 failure:
>
>
> On 28 Apr 2019, at 22:55, Chris Withers wrote:
>
>> On 28/04/2019 22:21, Robert Collins wrote:
>> Thank you!
>
> Thank me when we get there ;-) Currently in Dec 2018 with a wonderful Py2
> failure:
>
> ==
> ERROR:
On 28/04/2019 22:21, Robert Collins wrote:
Thank you!
Thank me when we get there ;-) Currently in Dec 2018 with a wonderful
Py2 failure:
==
ERROR: test_autospec_getattr_partial_function
Thank you!
If I understand correctly this is just the hg style branch backport
consequence, multiple copies of a change. Should be safe to skip those.
Rob
On Sun, 28 Apr 2019, 07:11 Chris Withers, wrote:
> Hi All,
>
> I'm in the process of bringing the mock backport up to date, but this
> has
On Sun, 28 Apr 2019 08:25:30 +0100
Chris Withers wrote:
>
> What's the best way to spell "show me all the revisions on master that
> affect {mock files} from commit x to HEAD, not including x"?
Something like:
$ git log x...HEAD -- {mock files}
perhaps?
Regards
Antoine.
FYI I pushed my 3 changes to implement my idea. It is now possible to
install some extensions in release mode and some others in debug mode.
Python in debug mode prefers debug extensions. I documented changes here:
On 28/04/2019 03:51, Martin Panter wrote:
On Sat, 27 Apr 2019 at 19:07, Chris Withers wrote:
Right, so I've merged up to 15f44ab043, what comes next?
$ git log --oneline --no-merges 15f44ab043.. -- Lib/unittest/mock.py
Lib/unittest/test/testmock/ | tail -n 3
This Git command line means
On 28/04/2019 03:51, Martin Panter wrote:
On Sat, 27 Apr 2019 at 19:07, Chris Withers wrote:
Right, so I've merged up to 15f44ab043, what comes next?
$ git log --oneline --no-merges 15f44ab043.. -- Lib/unittest/mock.py
Lib/unittest/test/testmock/ | tail -n 3
This Git command line means list