From: Nikolay Shustov <nikolay.shustov@gmail.com>
Date: Tue, 25 Mar 2025 23:54:55 GMT
Subject: Re: [Question] Moving from Python2 to Python3
Message-ID: <6977f08e-3c49-4bcc-9ab7-e3cc61a78396@gmail.com>
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?
>