Am 17.01.2024 um 19:44 schrieb Mats Wichmann via Python-list:
Be interesting to know if your WIndows 10 has those files in place, and
it's just a missing path entry (a good thing, perhaps) that's causing it
not to be found there.
Yes. Python is not on the Path - by design.
while the new
Am 16.01.2024 um 23:44 schrieb Barry via Python-list:
On 16 Jan 2024, at 17:11, Sibylle Koczian via Python-list
wrote:
while the new Windows 11 machine finds the Microsoft stub
You can turn off the stub in windows settings. The magic windows jargon is
“App Execution Aliases”. Once you
On 1/16/24 10:00, Sibylle Koczian via Python-list wrote:
Am 15.01.2024 um 23:55 schrieb Mats Wichmann via Python-list:
On 1/15/24 12:01, Thomas Passin via Python-list wrote:
On 1/15/2024 1:26 PM, Mats Wichmann via Python-list wrote:
Python from the App Store is not the same as Python from
> On 16 Jan 2024, at 17:11, Sibylle Koczian via Python-list
> wrote:
>
> while the new Windows 11 machine finds the Microsoft stub
You can turn off the stub in windows settings. The magic windows jargon is
“App Execution Aliases”. Once you find it in settings you can turn off
the python and
Am 15.01.2024 um 23:55 schrieb Mats Wichmann via Python-list:
On 1/15/24 12:01, Thomas Passin via Python-list wrote:
On 1/15/2024 1:26 PM, Mats Wichmann via Python-list wrote:
Python from the App Store is not the same as Python from python.org:
yes. this question is about the python.org
On 1/15/2024 7:24 PM, Thomas Passin wrote:
On 1/15/2024 6:27 PM, Greg Ewing via Python-list wrote:
On 16/01/24 11:55 am, Mats Wichmann wrote:
Windows natively has something called python.exe and python3.exe
which is interfering here
I'm wondering whether py.exe should be taught to recognise
On 1/15/2024 6:27 PM, Greg Ewing via Python-list wrote:
On 16/01/24 11:55 am, Mats Wichmann wrote:
Windows natively has something called python.exe and python3.exe which
is interfering here
I'm wondering whether py.exe should be taught to recognise these stubs
and ignore them. This sounds
On 16/01/24 11:55 am, Mats Wichmann wrote:
Windows
natively has something called python.exe and python3.exe which is
interfering here
I'm wondering whether py.exe should be taught to recognise these stubs
and ignore them. This sounds like something that could trip a lot of
people up.
--
Greg
On 1/15/24 12:01, Thomas Passin via Python-list wrote:
On 1/15/2024 1:26 PM, Mats Wichmann via Python-list wrote:
On 1/15/24 09:44, Sibylle Koczian via Python-list wrote:
First and foremost I want to understand why I'm seeing this:
- Python scripts with "/usr/bin/env python3" as shebang line
On 1/15/2024 1:26 PM, Mats Wichmann via Python-list wrote:
On 1/15/24 09:44, Sibylle Koczian via Python-list wrote:
First and foremost I want to understand why I'm seeing this:
- Python scripts with "/usr/bin/env python3" as shebang line work as
expected on a computer with Windows 10 and
On 1/15/24 09:44, Sibylle Koczian via Python-list wrote:
In the Python documentation for versions 3.11 and 3.12 I found no
differences regarding py.exe and shebang lines.
Then I removed the "/env" from the shebang lines and could start the
scripts from the second computer. That certainly is
On 1/15/24 09:44, Sibylle Koczian via Python-list wrote:
First and foremost I want to understand why I'm seeing this:
- Python scripts with "/usr/bin/env python3" as shebang line work as
expected on a computer with Windows 10 and Python 3.11.5. They have
worked for years on this machine,
Am 15.01.2024 um 00:46 schrieb Mike Dewhirst via Python-list:
In Windows the provided methods for running complex command lines are either a
batch file or a shortcut.Someone very kindly pointed out to me in this thread
that there is a PEP for py.exe. I don't use py.exe originally because I
) To:
python-list@python.org Subject: Re: Python 3.12.1, Windows 11: shebang line
#!/usr/bin/env python3
doesn't work any more Am 09.01.2024 um 12:36 schrieb Barry Scott via
Python-list:> > >> On 7 Jan 2024, at 15:09, Sibylle Koczian via Python-list
wrote:>>>>
On 1/14/2024 8:54 AM, Thomas Passin via Python-list wrote:
On 1/14/2024 7:48 AM, Sibylle Koczian via Python-list wrote:
Am 09.01.2024 um 12:36 schrieb Barry Scott via Python-list:
On 7 Jan 2024, at 15:09, Sibylle Koczian via Python-list
wrote:
Oh, and the two Windows and Python versions
On 1/14/2024 7:48 AM, Sibylle Koczian via Python-list wrote:
Am 09.01.2024 um 12:36 schrieb Barry Scott via Python-list:
On 7 Jan 2024, at 15:09, Sibylle Koczian via Python-list
wrote:
Oh, and the two Windows and Python versions are on two different
computers.
Will remove the "/env"
Am 09.01.2024 um 12:36 schrieb Barry Scott via Python-list:
On 7 Jan 2024, at 15:09, Sibylle Koczian via Python-list
wrote:
Oh, and the two Windows and Python versions are on two different computers.
Will remove the "/env" from my shebang lines, even if I don't understand what's
> On 7 Jan 2024, at 15:09, Sibylle Koczian via Python-list
> wrote:
>
> Oh, and the two Windows and Python versions are on two different computers.
>
> Will remove the "/env" from my shebang lines, even if I don't understand
> what's happening.
Thanks for the details.
Only thing I can
Am 01.01.2024 um 12:50 schrieb Barry via Python-list:
On 1 Jan 2024, at 11:14, Sibylle Koczian via Python-list
wrote:
But in all this thread I didn't see a single explanation for my current
situation: one and the same shebang line works on Windows 10 / Python 3.11 and
doesn't work on
> On 2 Jan 2024, at 17:24, Thomas Passin via Python-list
> wrote:
>
> You might learn about this if you happen to read and remember the right part
> of the Python docs. Otherwise you have no idea what py.exe is up to nor how
> it does it. I would say that most people don't know there's
On 1/2/2024 11:56 AM, Mats Wichmann via Python-list wrote:
On 1/1/24 12:53, Thomas Passin via Python-list wrote:
On Windows 10, a shebang line gets ignored in favor of Python 3.9.9
(if invoked by the script name alone) or Python 3.12.1 (if invoked by
the "py" launcher).
fwiw, you can also
On 1/1/24 12:53, Thomas Passin via Python-list wrote:
On Windows 10, a shebang line gets ignored in favor of Python 3.9.9 (if
invoked by the script name alone) or Python 3.12.1 (if invoked by the
"py" launcher).
fwiw, you can also create an ini file to define to the launcher py which
On 1/1/2024 12:26 PM, Mats Wichmann via Python-list wrote:
On 1/1/24 07:11, Thomas Passin via Python-list wrote:
Here's how to find out what program Windows thinks it should use to
run a ".py" file. In a console:
C:\Users\tom>assoc .py
.py=Python.File
C:\Users\tom>ftype Python.file
On 1/1/24 07:11, Thomas Passin via Python-list wrote:
Here's how to find out what program Windows thinks it should use to run
a ".py" file. In a console:
C:\Users\tom>assoc .py
.py=Python.File
C:\Users\tom>ftype Python.file
Python.file="C:\Windows\py.exe" "%L" %*
That's not enough. There
On 1/1/24 04:02, Sibylle Koczian via Python-list wrote:
Am 30.12.2023 um 04:04 schrieb Mike Dewhirst via Python-list:
I had assumed the OP had installed Python from the Microsoft shop and
that's where py.exe must have come from.
In fact I didn't say in my post that I always get Python
On 1/1/2024 8:19 AM, Thomas Passin via Python-list wrote:
On 1/1/2024 6:02 AM, Sibylle Koczian via Python-list wrote:
Am 30.12.2023 um 04:04 schrieb Mike Dewhirst via Python-list:
I had assumed the OP had installed Python from the Microsoft shop and
that's where py.exe must have come from.
On 1/1/2024 6:02 AM, Sibylle Koczian via Python-list wrote:
Am 30.12.2023 um 04:04 schrieb Mike Dewhirst via Python-list:
I had assumed the OP had installed Python from the Microsoft shop and
that's where py.exe must have come from.
In fact I didn't say in my post that I always get Python
> On 1 Jan 2024, at 11:14, Sibylle Koczian via Python-list
> wrote:
>
> But in all this thread I didn't see a single explanation for my current
> situation: one and the same shebang line works on Windows 10 / Python 3.11
> and doesn't work on Windows 11 / Python 3.12. I suspect Windows,
Am 30.12.2023 um 04:04 schrieb Mike Dewhirst via Python-list:
I had assumed the OP had installed Python from the Microsoft shop and
that's where py.exe must have come from.
In fact I didn't say in my post that I always get Python from
python.org. When I started to use the language there
On Sat, 30 Dec 2023 at 14:06, Mike Dewhirst via Python-list
wrote:
>
> On 29/12/2023 12:09 pm, Félix An via Python-list wrote:
> > On 2023-12-25 12:36, Mike Dewhirst wrote:
> >>
> >> 3. You cannot trust Microsoft. You can trust Python Software
> >> Foundation. Python from PSF works the same in
On 29/12/2023 12:09 pm, Félix An via Python-list wrote:
On 2023-12-25 12:36, Mike Dewhirst wrote:
3. You cannot trust Microsoft. You can trust Python Software
Foundation. Python from PSF works the same in all environments - or
if not it is a bug. Python from Microsoft is tweaked to satisfy
On Fri, 29 Dec 2023 at 12:23, Félix An via Python-list
wrote:
>
> On 2023-12-25 12:36, Mike Dewhirst wrote:
> >
> > 3. You cannot trust Microsoft. You can trust Python Software Foundation.
> > Python from PSF works the same in all environments - or if not it is a bug.
> > Python from Microsoft
On 2023-12-25 12:36, Mike Dewhirst wrote:
3. You cannot trust Microsoft. You can trust Python Software Foundation. Python
from PSF works the same in all environments - or if not it is a bug. Python
from Microsoft is tweaked to satisfy their aforementioned strategy of locking
in users to
-list Subject: Re: Python 3.12.1, Windows
11: shebang line #!/usr/bin/env python3
doesn't work any more On Mon, 25 Dec 2023 at 15:42, Mike Dewhirst via
Python-list wrote:>> Apologies for top posting - my
phone seems unable to do otherwise.>> Here's my view - which may not be
po
On Sun, 24 Dec 2023 22:55:34 +, Barry wrote:
>> On 24 Dec 2023, at 00:54, rbowman via Python-list
>> wrote:
>>
>> Does that work with virtualenv or conda? I'm slowly getting up to speed
>> with those.
>
> Conda is its own thing, not need for py.exe.
>
> Once you have created the venv you
On Mon, 25 Dec 2023 at 15:42, Mike Dewhirst via Python-list
wrote:
>
> Apologies for top posting - my phone seems unable to do otherwise.
>
> Here's my view - which may not be popular.
You're right about that part, anyhow :)
> 4. Shebang lines are pretty much redundant now that most python
Apologies for top posting - my phone seems unable to do otherwise.
Here's my view - which may not be popular.
1. Py.exe is an awful idea.
2. Installing python in %PROGRAMFILES% is not a good idea
3. Installing Python from a Microsoft shop or server is a bad idea
4. Shebang lines are pretty
> On 24 Dec 2023, at 00:54, rbowman via Python-list
> wrote:
>
> Does that work with virtualenv or conda? I'm slowly getting up to speed
> with those.
Conda is its own thing, not need for py.exe.
Once you have created the venv you do not need py.exe as you will have
pythob.exe in the venv
On 12/22/23 20:16, rbowman via Python-list wrote:
> On Fri, 22 Dec 2023 17:27:58 -0700, Michael Torrie wrote:
>
>> Using the py launcher as your Windows association with .py and.pyw files
>> you can have multiple versions of python installed and everything works
>> as it should, according to your
On Fri, 22 Dec 2023 17:27:58 -0700, Michael Torrie wrote:
> Using the py launcher as your Windows association with .py and.pyw files
> you can have multiple versions of python installed and everything works
> as it should, according to your shebang, just like on Unix.
Does that work with
On 12/22/23 20:56, Thomas Passin via Python-list wrote:
> It's just better not to make assumptions about which version of Python
> will be running. Just specify it yourself when you can, and then you can
> be sure.
Precisely, which is why the shebang is so useful, even on Windows with
py
> On 23 Dec 2023, at 03:01, Thomas Passin via Python-list
> wrote:
>
> Not on my system. It may depend on whether Python gets installed to Program
> Files or to %USERPROFILE%/AppData/Local/Programs/Python. Python 3.9 is the
> last verson I installed to Program Files, and that's the
On 2023-12-22 22:56:45 -0500, Thomas Passin via Python-list wrote:
> In my experience one should always make sure to know what version of Python
> is being used, at least if there is more than one version installed on the
> computer. Even on Linux using a shebang line can be tricky, because you
On 12/22/2023 7:27 PM, Michael Torrie via Python-list wrote:
On 12/22/23 07:02, Thomas Passin via Python-list wrote:
On my Windows 10 machine, Python scripts run without a shebang line.
Perhaps Windows 11 has added the ability to use one, but then you would
need to use the actual location of
On 12/22/2023 7:19 PM, Barry wrote:
On 23 Dec 2023, at 00:15, Thomas Passin via Python-list
wrote:
In neither case is the shebang line used.
As i understand it, not in front of my windows box to check.
The handler for .py file extension is set to be the py.exe
It is py.exe that
On 12/22/23 07:02, Thomas Passin via Python-list wrote:
> On my Windows 10 machine, Python scripts run without a shebang line.
> Perhaps Windows 11 has added the ability to use one, but then you would
> need to use the actual location of your Python executable.
Yes if you associate .py or .pyw
On 12/22/23 11:42, Thomas Passin via Python-list wrote:
> There is some important context that is missing here. Python on Windows
> does not normally install to that location. That is not even a Windows
> path, neither by directory name nor by path separators.
No, that's just the way the py
> On 23 Dec 2023, at 00:15, Thomas Passin via Python-list
> wrote:
>
> In neither case is the shebang line used.
As i understand it, not in front of my windows box to check.
The handler for .py file extension is set to be the py.exe
It is py.exe that understands shebang lines.
Barry
--
On 12/22/2023 9:29 AM, Sibylle Koczian via Python-list wrote:
Am 22.12.2023 um 14:13 schrieb Barry:
On 22 Dec 2023, at 12:39, Sibylle Koczian via Python-list
wrote:
Hello,
I always install Python on Windows in the same manner:
- Python is not on the path,
- it is installed for all
On 12/22/2023 7:36 AM, Sibylle Koczian via Python-list wrote:
Hello,
I always install Python on Windows in the same manner:
- Python is not on the path,
- it is installed for all users,
- the Python Launcher is installed for all users,
- the file types .py, .pyw etc. are associated with
> On 22 Dec 2023, at 14:58, Christian Buhtz via Python-list
> wrote:
>
> On Windows 11 it usually is the "Terminal" which is different from cmd.exe.
In terminal app you can run cmd.exe or powershell, so it is basically the same.
Barry
--
> On 22 Dec 2023, at 14:29, Sibylle Koczian wrote:
>
> #!/usr/bin/env/python
That was what i thought you had and it will not work.
The BOM suggestion is worth trying.
Barry
--
https://mail.python.org/mailman/listinfo/python-list
What is the "command line" on your Windows 11?
On Windows 10 it usually is "cmd.exe" (Windows Command Prompt).
On Windows 11 it usually is the "Terminal" which is different from
cmd.exe.
--
https://mail.python.org/mailman/listinfo/python-list
On 22/12/2023 13.36, Sibylle Koczian wrote:
Hello,
I always install Python on Windows in the same manner:
- Python is not on the path,
- it is installed for all users,
- the Python Launcher is installed for all users,
- the file types .py, .pyw etc. are associated with Python.
My shebang line
Am 22.12.2023 um 14:13 schrieb Barry:
On 22 Dec 2023, at 12:39, Sibylle Koczian via Python-list
wrote:
Hello,
I always install Python on Windows in the same manner:
- Python is not on the path,
- it is installed for all users,
- the Python Launcher is installed for all users,
- the file
> On 22 Dec 2023, at 12:39, Sibylle Koczian via Python-list
> wrote:
>
> Hello,
>
> I always install Python on Windows in the same manner:
>
> - Python is not on the path,
> - it is installed for all users,
> - the Python Launcher is installed for all users,
> - the file types .py, .pyw
Hello,
I always install Python on Windows in the same manner:
- Python is not on the path,
- it is installed for all users,
- the Python Launcher is installed for all users,
- the file types .py, .pyw etc. are associated with Python.
My shebang line is usually "#!/usr/bin/env python3".
This
57 matches
Mail list logo
