From: Pete Wyckoff <pw@padd.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Sebastian Morr <sebastian@morr.cc>,
git@vger.kernel.org, srabbelier@gmail.com
Subject: Re: [PATCH] Use Python's "print" as a function, not as a keyword
Date: Tue, 27 Dec 2011 11:41:31 -0500 [thread overview]
Message-ID: <20111227164131.GB29842@padd.com> (raw)
In-Reply-To: <CACBZZX7PVyCFfHTJN_QZfyt5wAcr4UAiJSmo54PSi=8pgv3sYA@mail.gmail.com>
avarab@gmail.com wrote on Wed, 21 Dec 2011 03:48 +0100:
> On Wed, Dec 21, 2011 at 03:19, Sebastian Morr <sebastian@morr.cc> wrote:
>
> > But, as nobody seems to have cared before: Is Git designed to be
> > compatible only with versions prior 3.0?
>
> I'm running Debian unstable and it has Python 2.7. Most people are
> still using Python 2.x as their default system Python since 3.x breaks
> backwards compatibility for common constructs like print.
>
> Does this only break Python 2.6, or all 2.x versions of Python?
>
> What's our currently supported Python version for the Python code in
> Git? It's 5.8.0 for Perl, do we have any particular aim for a
> supported Python version?
I test contrib/fast-import/git-p4 on python 2.5 and 2.7. I'm
hesitant to convert print() now, without committing to testing on
post-3.0 too. The work to support 3.x doesn't buy us much.
-- Pete
next prev parent reply other threads:[~2011-12-27 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 2:19 [PATCH] Use Python's "print" as a function, not as a keyword Sebastian Morr
2011-12-21 2:48 ` Ævar Arnfjörð Bjarmason
2011-12-21 16:12 ` Sverre Rabbelier
2011-12-27 16:41 ` Pete Wyckoff [this message]
2011-12-21 8:43 ` Frans Klaver
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=20111227164131.GB29842@padd.com \
--to=pw@padd.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=sebastian@morr.cc \
--cc=srabbelier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.