All of lore.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: rsbecker@nexbridge.com
Cc: git@vger.kernel.org
Subject: Re: [Question] Moving from Python2 to Python3
Date: Tue, 25 Mar 2025 21:31:18 +0000	[thread overview]
Message-ID: <Z-MgpuxFQ3xEgvsU@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <022b01db9d99$e68785c0$b3969140$@nexbridge.com>

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On 2025-03-25 at 15:23:40, rsbecker@nexbridge.com wrote:
> Hi Git Team,
> 
> I have Python2 and Python3 on my system. We are deprecating Python2 ASAP. Is
> there an easy way to force git
> to use Python3 only? Both are in /usr/bin. python has a symbolic link to
> python2 right now, but we are probably
> going to change that. I already have modified settings in config.mak.uname
> PYTHON_PATH = /usr/bin/python3.

I think only git-p4 uses Python in our codebase, so changing `PYTHON_PATH`
should be sufficient to fix it.  As far as I know, git-p4 currently
supports both, so things should just work.

Of course, I might be mistaken, since I don't use git-p4.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2025-03-25 21:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 15:23 [Question] Moving from Python2 to Python3 rsbecker
2025-03-25 21:31 ` brian m. carlson [this message]
2025-03-25 22:40   ` Nikolay Shustov
2025-03-25 23:19     ` Junio C Hamano
2025-03-25 23:54       ` Nikolay Shustov
2025-03-26  1:02         ` Todd Zullinger
2025-03-26  1:56           ` Nikolay Shustov

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=Z-MgpuxFQ3xEgvsU@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=rsbecker@nexbridge.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.