From: Yang Zhao <yang.zhao@skyboxlabs.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Git Users" <git@vger.kernel.org>
Subject: Re: yz/p4-py3, was Re: What's cooking in git.git (Jan 2020, #04; Wed, 22)
Date: Thu, 23 Jan 2020 10:27:36 -0800 [thread overview]
Message-ID: <CABvFv3KRAA9i75qBWDpnOro+CKRfqtPbh+LwpB1+EN+GwRGkkQ@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2001231306351.46@tvgsbejvaqbjf.bet>
On Thu, Jan 23, 2020 at 4:11 AM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Should we declare `t98xx` to be the namespace for the Python-based
> scripts, or alternatively declare that we won't ever include another
> Python script but `git-p4`?
Seeing how git-p4 has de facto taken over t98xx, declaring the former
makes sense. I intend to introduce more features into git-p4 so it'll
probably be practical to reserve more of the space for it, probably up
to t9850.
On declaring `git-p4` the sole approved use of python, I'm personally
OK with it if there's no appetite to better integrate Python on
Windows.
> But yes, I think that we should probably "tack on" the Python 3.x tests to
> the `linux-gcc` job.
>
> Or maybe finally split this job into three: ...
>
> The reason to split it off is this: on rare occasion, I have to restart
> the `linux-gcc` job because _one_ of those `git-p4` tests failed due to
> some reason or other, probably timing-related, I did not have time to
> investigate this. Having to re-run the entire test suite, twice, just to
> work around those flaky tests is rather wasteful.
Agreed.
--
yang
next prev parent reply other threads:[~2020-01-23 18:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 22:18 What's cooking in git.git (Jan 2020, #04; Wed, 22) Junio C Hamano
2020-01-22 22:37 ` Elijah Newren
2020-01-22 22:45 ` Junio C Hamano
2020-01-22 23:53 ` SZEDER Gábor
2020-01-23 6:06 ` Junio C Hamano
2020-01-23 12:11 ` yz/p4-py3, was " Johannes Schindelin
2020-01-23 18:27 ` Yang Zhao [this message]
2020-01-27 12:55 ` SZEDER Gábor
2020-01-23 14:16 ` SZEDER Gábor
2020-01-23 17:56 ` SZEDER Gábor
2020-01-23 20:52 ` Junio C Hamano
2020-01-24 17:45 ` Yang Zhao
2020-01-25 0:13 ` Johannes Schindelin
2020-01-25 8:31 ` SZEDER Gábor
2020-01-26 9:21 ` Johannes Schindelin
2020-01-23 21:39 ` Johannes Schindelin
2020-01-24 12:02 ` SZEDER Gábor
2020-01-25 0:35 ` Johannes Schindelin
2020-02-05 21:01 ` Junio C Hamano
2020-02-06 0:27 ` SZEDER Gábor
2020-02-06 8:57 ` Johannes Schindelin
2020-02-06 9:06 ` SZEDER Gábor
2020-02-06 11:45 ` Johannes Schindelin
2020-01-23 11:56 ` Johannes Schindelin
2020-01-23 4:29 ` Denton Liu
2020-01-23 6:08 ` Junio C Hamano
2020-01-23 16:54 ` Christian Couder
2020-01-23 20:23 ` Junio C Hamano
2020-01-26 20:07 ` Denton Liu
2020-01-27 18:29 ` Junio C Hamano
2020-01-27 20:26 ` [PATCH] .mailmap: fix erroneous authorship for Derrick Stolee Denton Liu
2020-01-28 17:56 ` Junio C Hamano
2020-01-29 8:59 ` What's cooking in git.git (Jan 2020, #04; Wed, 22) Denton Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABvFv3KRAA9i75qBWDpnOro+CKRfqtPbh+LwpB1+EN+GwRGkkQ@mail.gmail.com \
--to=yang.zhao@skyboxlabs.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).