unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: guix-devel@gnu.org, Ricardo Wurmus <rekado@elephly.net>
Subject: Re: python2 in git
Date: Tue, 03 Mar 2020 12:53:07 +0000	[thread overview]
Message-ID: <63DD2665-853A-4862-A201-05576FB61503@gmail.com> (raw)
In-Reply-To: <875zflhamm.fsf@elephly.net>

Hi Ricardo!

On March 3, 2020 12:43:29 PM UTC, Ricardo Wurmus <rekado@elephly.net> wrote:
>Hi Guix,
>
>our “git” package has python-2 among its inputs.  It says this:
>
>("python" ,python-2) ; CAVEAT: incompatible with python-3 according to
>INSTALL
>
>The INSTALL file for git 2.25.1 says this about Python:
>
>	- Python version 2.4 or later (but not 3.x, which is not
>	  supported by Perforce) is needed to use the git-p4 interface
>	  to Perforce.
>
>The git-p4 script does, however, contain conditionals to accomodate
>Python 3.  Here’s an example:
>
>--8<---------------cut here---------------start------------->8---
># support basestring in python3
>try:
>    unicode = unicode
>except NameError:
>    # 'unicode' is undefined, must be Python 3
>    str = str
>    unicode = str
>    bytes = bytes
>    basestring = (str,bytes)
>else:
>    # 'unicode' exists, must be Python 2
>    str = str
>    unicode = unicode
>    bytes = str
>    basestring = basestring
>--8<---------------cut here---------------end--------------->8---
>
>It also uses the Python 3 style “print” call instead of the Python 2
>style statement.
>
>I would like to build git with the latest version of Python.  Any
>objections?

Good analysis! None from me!

Maxim

  reply	other threads:[~2020-03-03 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 12:43 python2 in git Ricardo Wurmus
2020-03-03 12:53 ` Maxim Cournoyer [this message]
2020-03-03 13:32 ` Tobias Geerinckx-Rice

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63DD2665-853A-4862-A201-05576FB61503@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).