On Thu, 26 Mar 2020 at 22:11, Cameron Simpson wrote:
>
> It seems to me that there is a deliberate choice to _not_ install the
> "python3" executable name when installing Python 3 on Windows, and to my
> eye that is/was a _bad_ choice. I would like to see a good explaination
> as to why that choic
On 23Mar2020 17:59, Frédéric De Jaeger wrote:
There is a recurring problem in my company where we use python in
various places (python3).
We do cross platform development windows/linux and our python scripts need to
run everywhere.
Some scripts are launched manually in a terminal.
Others are l
> On 25 Mar 2020, at 17:02, Andrew Barnert wrote:
>
> On Mar 25, 2020, at 05:02, Paul Moore wrote:
>>
>> The only reason anyone has ever suggested versioned executables on
>> Windows is for Unix compatibility - the reasons they are needed on
>> Unix simply don't apply on Windows (at least not
On Wed, Mar 25, 2020 at 9:57 AM Paul Moore wrote:
> On Wed, 25 Mar 2020 at 16:10, Eryk Sun wrote:
>
> > The py launcher's "env" command searches PATH for anything from
> > "python" to "notepad" -- but not for a versioned Python command such
> > as "python3" or "python2". It always uses a regist
On Thu, 26 Mar 2020 at 15:52, Barry Scott wrote:
>
> > On 25 Mar 2020, at 16:53, Paul Moore wrote:
> >
> > On Wed, 25 Mar 2020 at 16:10, Eryk Sun wrote:
> >
> >> The py launcher's "env" command searches PATH for anything from
> >> "python" to "notepad" -- but not for a versioned Python command s
> On 25 Mar 2020, at 16:53, Paul Moore wrote:
>
> On Wed, 25 Mar 2020 at 16:10, Eryk Sun wrote:
>
>> The py launcher's "env" command searches PATH for anything from
>> "python" to "notepad" -- but not for a versioned Python command such
>> as "python3" or "python2". It always uses a registe
