From: Todd Zullinger <tmz@pobox.com>
To: Nikolay Shustov <nikolay.shustov@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
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 21:02:18 -0400 [thread overview]
Message-ID: <Z-NSGtV06NPE_C9D@teonanacatl.net> (raw)
In-Reply-To: <6977f08e-3c49-4bcc-9ab7-e3cc61a78396@gmail.com>
Nikolay Shustov wrote:
> 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").
Perhaps you were conflating PYTHON_PATH, which brian
suggested, with PYTHONPATH?
PYTHON_PATH is used by the git build system to set the path
to the python executable, e.g.: /usr/bin/python2,
/usr/bin/python3, etc.
PYTHONPATH is used by python itself to point to the
location(s) of module files, similar to PATH, as you
mentioned.
The Fedora distribution packaging set PYTHON_PATH to python2
or python3 while both were available and things worked well.
Only python3 is supported now, and PYTHON_PATH is set
accordingly.
That ought to work just as well for NonStop. If it doesn't,
that would most likely be something to take up with the OS
folks handling python3. :)
--
Todd
next prev parent reply other threads:[~2025-03-26 1:02 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
2025-03-26 1:02 ` Todd Zullinger [this message]
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-NSGtV06NPE_C9D@teonanacatl.net \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nikolay.shustov@gmail.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 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.