Doh! Of course I thought of PYTHONPATH not of PYTHON_PATH.
My apologies for the noise.
On 3/25/25 21:02, Todd Zullinger wrote:
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. :)
