On 4/11/20, Barry Scott wrote:
>> On 10 Apr 2020, at 20:14, Christopher Barker wrote:
>>
>> Also, if order to get python top level scripts to work, there needs to be
>> a PATH entry for that, too.
>
> Do you mean the #! lines? That is taken care of by py.exe and how it was
> installed.
I think b
> On 10 Apr 2020, at 20:14, Christopher Barker wrote:
>
> I rarely use Windows, but do support them, so this sounds good to me.
>
> But one confusion:
>
> With py.exe no need to mess with the PATH.
>
> How does py.exe get on the PATH?
>
> Now that the need for python 2 and 3 on the same mac
On 4/10/20, MRAB wrote:
> On 2020-04-10 20:14, Christopher Barker wrote:
>
>> How does py.exe get on the PATH?
>>
> py.exe goes into the Windows folder, which is on the PATH.
That's the typical setup, but a standard user that can't get OTS
administrator access has to install the launcher just for
On 2020-04-10 20:14, Christopher Barker wrote:
I rarely use Windows, but do support them, so this sounds good to me.
But one confusion:
With py.exe no need to mess with the PATH.
How does py.exe get on the PATH?
py.exe goes into the Windows folder, which is on the PATH.
Now that the ne
I rarely use Windows, but do support them, so this sounds good to me.
But one confusion:
With py.exe no need to mess with the PATH.
>
How does py.exe get on the PATH?
Now that the need for python 2 and 3 on the same machine is greatly reduced
-- is it so bad to put python.exe on the PATH?
Also
