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
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 in my experience -
> it's possible that some peoplehave workf
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 registered installation
> in this case, which is at the very least
On 3/25/20, Barry Scott wrote:
>> On 25 Mar 2020, at 09:15, Eryk Sun wrote:
>>
>> That is not consistent with Unix. env is supposed to search PATH for
>> the command. However, the launcher does not search PATH for a
>> versioned command such as "python3". Instead it uses the highest
>> version th
On Wed, 25 Mar 2020 at 11:43, Barry Scott wrote:
> I think the reasoning is that the whole point of the py.exe is to avoid having
> users edit their PATH on Windows. And further the thinking goes that
> you do not need the alternatively named python programs.
The alternatively named programs have
> On 25 Mar 2020, at 09:15, Eryk Sun wrote:
>
> On 3/25/20, Steve Barnes wrote:
>>> Except it's not necessarily what the original post wants. The OP wants the
>>> shebang "#!/usr/bin/env python3" to "work everywhere by
>>> default", for which I assume it's implied that it should work consiste
On 3/25/20, Steve Barnes wrote:
>> Except it's not necessarily what the original post wants. The OP wants the
>> shebang "#!/usr/bin/env python3" to "work everywhere by
>> default", for which I assume it's implied that it should work consistently
>> everywhere. I'd prefer for the launcher's env se
On 3/25/20, Steve Barnes wrote:
> Of course if, rather than creating symlinks, you create a batch file called
> python3.bat and containing the line:
> @py -3 %*
Batch scripts execute via cmd.exe, with an attached console, and when
Ctrl+C is typed they display a "Terminate batch job (Y/N)?" prompt
On 3/24/20, Mike Miller wrote:
> On 2020-03-24 11:58, Eryk Sun wrote:
>
>> You can manually copy or symlink python.exe to python3.exe in the
>> installation directory and venv "Scripts" directories. However, it
>> will only be used on the command line, and other contexts that search
>> PATH. Curre
.docx") - the only real issue to avoid is
the fact that Windows paths are case insensitive so names that differ only in
case changes can & will collide.
-Original Message-
From: Mike Miller
Sent: 24 March 2020 21:39
To: python-ideas@python.org
Subject: [Python-ideas] Re: About
On 2020-03-24 11:58, Eryk Sun wrote:
On 3/24/20, Mike Miller wrote:
C:\Users\User>python3
(App store loads!!)
If installed, the app distribution has an appexec link for
"python3.exe" that actually works.
C:\Python38>dir
Volume in drive C has no label.
[snip]
Note
On Wed, Mar 25, 2020 at 7:29 AM Christopher Barker wrote:
>
> On Mon, Mar 23, 2020 at 6:19 PM Oleg Broytman wrote:
>>
>>
>> IMO the issue is in not following the best practices. Distribute wheels
>> or freezed binaries, not just drop scripts unto users.
>
>
> This is a good point, though I’m not
On Mon, Mar 23, 2020 at 6:19 PM Oleg Broytman wrote:
>
> IMO the issue is in not following the best practices. Distribute wheels
> or freezed binaries, not just drop scripts unto users.
>
This is a good point, though I’m not sure the best solution. Frozen
Binaries (py2exe, PyInstaller) are a goo
ric De Jaeger
> *Cc:* Python-ideas < >
> *Subject:* [Python-ideas] Re: About python3 on windows
>
>
>
> > That would be nice. Does it apply to the _windows store version_, the
> _traditional installer_, both ?
>
>
>
> I believe it only applies to the traditional
as] Re: About python3 on windows
> That would be nice. Does it apply to the _windows store version_, the
> _traditional installer_, both ?
I believe it only applies to the traditional installer from
python.org<http://python.org>. You will also have to verify it, as it has been
a decen
On 3/24/20, Mike Miller wrote:
>
> C:\Users\User>python3
> (App store loads!!)
If installed, the app distribution has an appexec link for
"python3.exe" that actually works.
> C:\Python38>dir
> Volume in drive C has no label.
> [snip]
> Note there is no python3.exe binary.
Y
On 2020-03-23 16:49, Brett Cannon wrote:
Recently I've had to use a Windows VM for some stuff at work, where I
installed
Python 3 as well. Every time I type python3 at the command-line (instead of
python) to use the repl, it tries to load the Microsoft App Store!
There is an opti
> That would be nice. Does it apply to the _windows store version_, the
_traditional installer_, both ?
I believe it only applies to the traditional installer from python.org. You
will also have to verify it, as it has been a decent while since I've had
to install Python on Windows.
On Tue, Mar
On 3/24/20, Barry Scott wrote:
>
> If you have python 2 and 3 installed then
>
>py -3 myscript
"myscript" may have a shebang that runs the "python2" virtual command
(e.g. "#!python2" or "#!/usr/bin/python2") because the script requires
2.x, but using "-3" will override it to run the "python3"
> This does work out of the box because py.exe is run when you execute a .py
> in the
> CMD.
Yep, but the constraint is it has to run in Cygwin's bash terminal. Does it
honor windows file associations ? I have some doubts (sorry I don't have a
windows available to test the hypothesis). If
On Tue, 24 Mar 2020 at 11:39, Eric V. Smith wrote:
> Cygwin should make it easier to have Windows look like Unix, not harder.
In my experience, only if you use Cygwin for everything (so I agree,
Frédéric should probably install cygwin Python). Integrating native
applications and Cygwin isn't hard
On Tue, 24 Mar 2020 at 09:41, Rhodri James wrote:
>
> On 24/03/2020 01:13, Oleg Broytman wrote:
> > IMO the issue is in not following the best practices. Distribute wheels
> > or freezed binaries, not just drop scripts unto users.
>
> For most circumstances, that is not a practical answer. Creati
On 3/24/2020 6:58 AM, Frédéric De Jaeger wrote:
One of our constraint is that we use Cygwin's bash and now, every user relies
on the shebang.
The problem reduce to this. Assuming you are in a bash window (whether on
cygwin or ubuntu 18, or mac os) and you do this:
> ./myScript.py
How
On Tue, Mar 24, 2020 at 10:21:33AM +, Barry Scott
wrote:
> > On 23 Mar 2020, at 17:59, Fr??d??ric De Jaeger
> > wrote:
> > The issue is: There is no reliable way to launch a python script.
> >
> > The command:
> >
> > python myscript.py
> >
> > launches python3 on windows and pyth
On Tue, Mar 24, 2020 at 09:40:07AM +, Rhodri James
wrote:
> I'm afraid the terseness of your answer didn't make it at all clear how
> creating venvs would solve Fred's problems. It still isn't obvious to me!
One doesn't create virtual environments every day; once a year may be.
And there ar
> Windows devices, they might want to consider using the PrependPath option
> (which adds Python to PATH from the command line). I.E.
> python-3.8.0.exe /quiet InstallAllUsers=1 PrependPath=1
> (IIRC, the above installation should allow usage of "python3" on
> Windows for all users on the device)
Steven D'Aprano wrote:
> On Mon, Mar 23, 2020 at 05:59:41PM -, Frédéric De Jaeger wrote:
> > The issue is: There is no reliable way to launch a
> > python script.
> > The command:
> > python myscript.py
> >
> > launches python3 on windows and python2 on 99% of the unix market.
> > Its probab
> On 23 Mar 2020, at 17:59, Frédéric De Jaeger wrote:
>
> Hi all,
>
> 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 m
On 24/03/2020 01:13, Oleg Broytman wrote:
On Tue, Mar 24, 2020 at 11:30:38AM +1100, Steven D'Aprano
wrote:
Fred is explicitly asking about the problem with having to sometimes use
python and sometimes python3, and your answer is to tell him to
sometimes use python and sometimes use python3?
On Tue, Mar 24, 2020 at 11:30:38AM +1100, Steven D'Aprano
wrote:
> On Tue, Mar 24, 2020 at 12:45:42AM +0100, Oleg Broytman wrote:
>
> > > Won't that create a virtual environment using Python3 on Windows and
> > > using Python2 most other places, which is exactly the problem Fred is
> > > havin
On Mon, Mar 23, 2020 at 05:59:41PM -, Frédéric De Jaeger wrote:
> The issue is: There is no reliable way to launch a python script.
>
> The command:
>
> python myscript.py
>
> launches python3 on windows and python2 on 99% of the unix market.
Its probably less than 99% by now, but
On Tue, Mar 24, 2020 at 12:45:42AM +0100, Oleg Broytman wrote:
> > Won't that create a virtual environment using Python3 on Windows and
> > using Python2 most other places, which is exactly the problem Fred is
> > having?
>
> Depends on how literally one reads ``python -m venv``.
I read it as
Brett Cannon wrote:
> There is an option to install Python to PATH on Windows if you check the
appropriate box during installation, but that's not really the
> way Windows apps typically work.
In this case of the OP, if they're mass installing Python on company
Windows devices, they might want to
On Mon, Mar 23, 2020 at 3:47 PM Mike Miller
wrote:
>
> On 2020-03-23 10:59, Frédéric De Jaeger wrote:
> > Hi all,
> >
> > There is a recurring problem
>
> Yep, that's a problem. I've built up a habit on Ubuntu where I type
> python3 a
> number of times a day, honed over several years. So far so
On Tue, Mar 24, 2020 at 10:22:28AM +1100, Steven D'Aprano
wrote:
> On Mon, Mar 23, 2020 at 08:09:57PM +0100, Oleg Broytman wrote:
> > On Mon, Mar 23, 2020 at 05:59:41PM -, Fr??d??ric De Jaeger
> > wrote:
> > > The issue is: There is no reliable way to launch a python script.
> > >
> > > T
On Mon, Mar 23, 2020 at 08:09:57PM +0100, Oleg Broytman wrote:
> On Mon, Mar 23, 2020 at 05:59:41PM -, Fr??d??ric De Jaeger
> wrote:
> > The issue is: There is no reliable way to launch a python script.
> >
> > The command:
> >
> > python myscript.py
> >
> > launches python3 on windo
On 2020-03-23 10:59, Frédéric De Jaeger wrote:
Hi all,
There is a recurring problem
Yep, that's a problem. I've built up a habit on Ubuntu where I type python3 a
number of times a day, honed over several years. So far so good.
Recently I've had to use a Windows VM for some stuff at work,
On Mon, Mar 23, 2020 at 05:59:41PM -, Fr??d??ric De Jaeger
wrote:
> The issue is: There is no reliable way to launch a python script.
>
> The command:
>
> python myscript.py
>
> launches python3 on windows and python2 on 99% of the unix market.
Create and activate a virtual environm
> On Mar 23, 2020, at 11:16, Frédéric De Jaeger wrote:
>
> The command:
>
>python myscript.py
>
> launches python3 on windows and python2 on 99% of the unix market.
While that’s true for Mac 10.14, Ubuntu 18.04 LTS, etc., I think almost
everyone is deprecating Python 2 in their current re
Hi Fred,
If windows users associate .py with the py.exe launcher, (and .pyw with the
pyw.exe launcher), then it will default to python 3 (highest version installed,
64 bit if available), and will honour a `#! python3` shebang, (with a number of
formats accepted). It should also be reasonably ea
45 matches
Mail list logo
