Re: yz/p4-py3, was Re: What's cooking in git.git (Feb 2020, #03; Wed, 12)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 13, 2020, 16:06 UTC
Message-ID: <xmqq7e0qtqsm.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <nycvar.QRO.7.76.6.2002131401130.46@tvgsbejvaqbjf.bet>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 18 quoted lines

> On Wed, 12 Feb 2020, Junio C Hamano wrote:
>
>> * yz/p4-py3 (2020-01-15) 14 commits
>>  . ci: also run linux-gcc pipeline with python3.5 environment
>>  - git-p4: use python3's input() everywhere
>>  ...
>>
>>  Update "git p4" to work with Python 3.
>>
>>  Hold.
>>  The last step is too wasteful to run full tests twice.
>>  cf. <20200122235333.GA6837@szeder.dev>
>>  cf. <20200123175645.GF6837@szeder.dev>
>
> All right, all right, all right! If we cannot find any better way than to
> just use Python2 in -clang and Python3 in -gcc (or was it the other way
> round, I forget), then we cannot find any better way, and I won't hold
> this up any longer.

OK, any one of you wants to do the honors of wrapping up the proposed patch with a log message to replace the tip commit to allow us to move forward?

Thanks.