git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Shustov <nikolay.shustov@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: rsbecker@nexbridge.com, git@vger.kernel.org,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [Question] Moving from Python2 to Python3
Date: Tue, 25 Mar 2025 19:54:55 -0400	[thread overview]
Message-ID: <6977f08e-3c49-4bcc-9ab7-e3cc61a78396@gmail.com> (raw)
In-Reply-To: <xmqqtt7glmut.fsf@gitster.g>

You are right, my answer was over-engineered.
Instead of speculating about what else needs to be done if one decides 
to set PYTHONPATH, I should have just advised to use the OS specific 
method on setting up the "default" Python as Python3 and be with it.
Well, unless the dual Python is needed (git-p4 running with the Python 
different from system "default").

On 3/25/25 19:19, Junio C Hamano wrote:
> Nikolay Shustov <nikolay.shustov@gmail.com> writes:
>
>> git-p4 is designed to work both with Python 2 and Python 3.
>>
>> However, changing just PYTHONPATH may not to be good enough.
>>
>> In general, it is necessary to make having PYTHONPATH value and the
>> version of Python executable which application is run by, to be
>> coherent: Python executable has to be able to work correctly with the
>> libraries PYTHONPATH points to.
> Hmph, but isn't that the core competence of those who package Python
> to their target system?  If we run something with /usr/bin/python3,
> without any strange customization, that binary ought to know where
> it should pull its associated standard library files from, and we as
> the language users do not have to worry about it, no?
>

  reply	other threads:[~2025-03-25 23:54 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
2025-03-25 22:40   ` Nikolay Shustov
2025-03-25 23:19     ` Junio C Hamano
2025-03-25 23:54       ` Nikolay Shustov [this message]
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=6977f08e-3c49-4bcc-9ab7-e3cc61a78396@gmail.com \
    --to=nikolay.shustov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rsbecker@nexbridge.com \
    --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).