git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Illia Bobyr <illia.bobyr@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
	Kapil Somani <kmsomani@alumni.ncsu.edu>,
	git@vger.kernel.org
Subject: Re: `git p4` broken on machines which do not have python on path
Date: Wed, 5 Feb 2025 18:16:00 -0800	[thread overview]
Message-ID: <101b03c5-dfad-41f0-8156-e541b8e6c68f@gmail.com> (raw)
In-Reply-To: <Z6QUeaoH_tV2ncwn@tapette.crustytoothpaste.net>

On 2/5/25 17:46, brian m. carlson wrote:
> I realize that Python 3 is now the default, but there were apparently
> still some people who want to use Python 2.7 last time this came up, so
> the default shebang hasn't changed. According to Python upstream,
> `python` can be of any version, although for all distros I'm aware of,
> `python` is always version 2.

I just checked my Ubuntu 24.10 and `python` is `python3`.

❯ python --version
Python 3.12.7

❯ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.10
Release:        24.10
Codename:       oracular

❯ whereis python
python: /usr/bin/python

❯ dpkg -S /usr/bin/python
python-is-python3: /usr/bin/python

There are both `python-is-python2` and `python-is-python3` packages.
They just provide a symlink for convenience.
And one can use Python version managers to manage what `python` means, 
of cause.


  reply	other threads:[~2025-02-06  2:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06  1:27 `git p4` broken on machines which do not have python on path Kapil Somani
2025-02-06  1:46 ` brian m. carlson
2025-02-06  2:16   ` Illia Bobyr [this message]
     [not found]   ` <CANF_+=7hM7QqLNE3d4=UO-8erYoeQwYG5SrsDTXtgqZq3AKJwg@mail.gmail.com>
2025-02-06 22:18     ` brian m. carlson
2025-02-06 23:17       ` Junio C Hamano

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=101b03c5-dfad-41f0-8156-e541b8e6c68f@gmail.com \
    --to=illia.bobyr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kmsomani@alumni.ncsu.edu \
    --cc=sandals@crustytoothpaste.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.
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).