git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Dan McGee <dan@archlinux.org>
Cc: GIT Mailing-list <git@vger.kernel.org>,
	Florian Achleitner <florian.achleitner.2.6.31@gmail.com>,
	David Michael Barr <b@rr-dav.id.au>,
	"Eric S. Raymond" <esr@thyrsus.com>
Subject: Re: Test failures with python versions when building git 1.8.1
Date: Tue, 01 Jan 2013 21:19:13 -0800	[thread overview]
Message-ID: <7va9ss5fhq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAEik5nOqge8ix4WGf-h+0Dmz1CanH_XtQdB-CxvPsggSu1-LzQ@mail.gmail.com> (Dan McGee's message of "Tue, 1 Jan 2013 22:12:17 -0600")

Dan McGee <dan@archlinux.org> writes:

> A test case snuck in this release that assumes /usr/bin/python is
> python2 and causes test failures. Unlike all other tests and code
> depending on python, this one does not respect PYTHON_PATH, which we
> explicitly set when building git on Arch Linux due to python2 vs
> python3 differences.

I had an impression that you are not supposed to run our scripts
with python3 yet (no python scripts have been checked for python3
compatibility), even though some people have expressed interests in
doing so.

Eric?

  reply	other threads:[~2013-01-02  5:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02  4:12 Test failures with python versions when building git 1.8.1 Dan McGee
2013-01-02  5:19 ` Junio C Hamano [this message]
2013-01-02  5:45   ` Eric S. Raymond
2013-01-02  6:53   ` Jeff King
2013-01-02  7:18     ` Junio C Hamano
2013-01-02  8:59       ` Jeff King
2013-01-02  9:09         ` Joachim Schmitz
2013-01-02 14:18         ` Dan McGee
2013-01-02 16:35           ` Junio C Hamano
2013-01-02 21:25             ` Dan McGee
2013-01-02 16:34         ` Junio C Hamano
2013-01-02 20:54           ` Jeff King

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=7va9ss5fhq.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=b@rr-dav.id.au \
    --cc=dan@archlinux.org \
    --cc=esr@thyrsus.com \
    --cc=florian.achleitner.2.6.31@gmail.com \
    --cc=git@vger.kernel.org \
    /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).