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
ebang line work as
expected on a computer with Windows 10 and Python 3.11.5. They have
worked for years on this machine, using either the latest Python or
one version before (depending on availability of some packages).
There is a virtual machine with ArchLinux on the same machine and
some of t
the second computer. That certainly is a solution, but
why???
It's because of Windows itself. The default nowadays is that irritating
little stub that prompts you to go install Python from the WIndows
store. When you use the "env" form, it looks for python (or python3 in
your case) in t
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 th
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 "
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 underst
> 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
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
don't know there's an ini file, let
> alone what it can do. Of course this situation isn't unique to py.exe!
On discuss.python.org we will share the link to the python windows docs and
often to this specific section:
https://docs.python.org/3/using/windows.html#python-launcher-for-windows
To
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
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,
because a change in the way Python 3.12 uses shebang lines should be
visible in the documentation.
The shebang support in the Python
source.
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, because a change in the way Python 3.12 uses shebang lines
should be visible
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,
because a change in the way Python 3.12 uses shebang lines should be
visible in the documentation.
Happy new year to all!
Sibylle
> 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.
works on Windows 10 / Python
3.11 and doesn't work on Windows 11 / Python 3.12. I suspect Windows,
because a change in the way Python 3.12 uses shebang lines should be
visible in the documentation.
Happy new year to all!
Sibylle
--
https://mail.python.org/mailman/listinfo/python-list
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
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 .p
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 w
> 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 Python
> 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
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 py
On 6/15/23, Thomas Schweikle via Python-list wrote:
>
> No. This flag is not inherited. Someone has to set it for created
> directories. It is easy to confirm: take a directory not under MSYS or
> cygwin control (because it is mounted by MSYS or cygwin), set the flag,
> then create directories.
Am Do., 15.Juni.2023 um 16:28:21 schrieb Eryk Sun:
On 6/15/23, Thomas Schweikle via Python-list wrote:
In this case: not sure what is going on.
Possibly you have a setting configured that affects the behavior of
Git via the MinGW-w64 runtime, such that calling mkdir() ends up
calling
Am Do., 15.Juni.2023 um 15:44:42 schrieb Inada Naoki:
Then, git doesn't enable Windows NTFS case sensitivity.
You enabled NTFS case sensitivity on "C:\Users\user\K".
And Windows enabled case sensitivity for all new directories under the
directory.
No. This flag is not inherited. Someone has
On 6/15/23, Thomas Schweikle via Python-list wrote:
>
> In this case: not sure what is going on.
Possibly you have a setting configured that affects the behavior of
Git via the MinGW-w64 runtime, such that calling mkdir() ends up
calling NtSetInformationFile() to set the
Then, git doesn't enable Windows NTFS case sensitivity.
You enabled NTFS case sensitivity on "C:\Users\user\K".
And Windows enabled case sensitivity for all new directories under the
directory.
Since it is not default and minor setting, it is not a bug that
current Python doesn't support
Am Mi., 14.Juni.2023 um 15:10:50 schrieb Eryk Sun:
On 6/14/23, Inada Naoki via Python-list wrote:
Since Git enables Windows NTFS case sensitivity while checking out sources
I didn't know that. Would you give us a link to this feature?
As far as I know, `git config core.ignorecase` doesn't
On 6/14/23, Inada Naoki via Python-list wrote:
>> Since Git enables Windows NTFS case sensitivity while checking out sources
>
> I didn't know that. Would you give us a link to this feature?
> As far as I know, `git config core.ignorecase` doesn't mean NTFS case
> sensitive.
If a repo is cloned
python-list@python.org> wrote:
> Hi!
>
> Trying to compile python on windows leads to following error:
>
>_testimportmultiple.vcxproj ->
>
> C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\amd64\_testimportmultiple.pyd
>_testmultiphase.c
> Bibliothek
Am Di., 13.Juni.2023 um 20:36:17 schrieb Mats Wichmann via Python-list:
On 6/13/23 12:12, Thomas Schweikle via Python-list wrote:
Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz:
What version of visual studio are you using?
Visual Studio 2022, aka 17.6.2.
What version of python?
On 6/13/23, Thomas Schweikle via Python-list wrote:
>
> Since Git enables Windows NTFS case sensitivity while checking out
> sources ... is it a bug or a "feature"? And: is there a simple
AFAIK the Windows version of Git (you're not using the Linux version
of Git via WSL, right?) does not
Tuesday, June 13, 2023 1:12 PM
To: Python
Cc: Thomas Schweikle
Subject: Re: Compiling python on windows with vs
Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz:
> What version of visual studio are you using?
Visual Studio 2022, aka 17.6.2.
> What version of python?
python 3.10.11 or 3
On 6/13/23 12:12, Thomas Schweikle via Python-list wrote:
Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz:
What version of visual studio are you using?
Visual Studio 2022, aka 17.6.2.
What version of python?
python 3.10.11 or 3.11.4
I’ve had success with using the cython package
Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz:
What version of visual studio are you using?
Visual Studio 2022, aka 17.6.2.
What version of python?
python 3.10.11 or 3.11.4
I’ve had success with using the cython package in python and cl from visual
studio, but I haven’t tried
What version of visual studio are you using? What version of python? I’ve had
success with using the cython package in python and cl from visual studio, but
I haven’t tried visual studio alone.
Sent from my iPhone
> On Jun 13, 2023, at 11:59 AM, Thomas Schweikle via Python-list
> wrote:
>
Hi!
Trying to compile python on windows leads to following error:
_testimportmultiple.vcxproj ->
C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\amd64\_testimportmultiple.pyd
_testmultiphase.c
Bibliothek
"C:\Users\sct-muc\Documents\Projekte\cpython\PCbui
On 3/28/2023 1:50 PM, a a wrote:
On Tuesday, 28 March 2023 at 18:12:40 UTC+2, Thomas Passin wrote:
On 3/28/2023 8:47 AM, a a wrote:
Ok, I can export bookmarks to html file and open it in Firefox to get
a long list of clickable urls but icon of the bookmarked web page is missing.
When I open
On Tuesday, 28 March 2023 at 18:12:40 UTC+2, Thomas Passin wrote:
> On 3/28/2023 8:47 AM, a a wrote:
> > Ok, I can export bookmarks to html file and open it in Firefox to get
> > a long list of clickable urls but icon of the bookmarked web page is
> > missing.
> >
> > When I open Bookmarks as
On 3/28/2023 8:47 AM, a a wrote:
Ok, I can export bookmarks to html file and open it in Firefox to get
a long list of clickable urls but icon of the bookmarked web page is missing.
When I open Bookmarks as right a side-bar I can view and identify an individual
Boomarks by icon,
so I would like
On Tuesday, 28 March 2023 at 06:33:44 UTC+2, Thomas Passin wrote:
> On 3/27/2023 8:37 PM, a a wrote:
> >> To save the tabs, right click any one of them and select the "Select All
> >> Tabs" item. They will all highlight. Right click on one of them and
> >> select the "Bookmark Tabs" item. A
On Tuesday, 28 March 2023 at 06:33:44 UTC+2, Thomas Passin wrote:
> On 3/27/2023 8:37 PM, a a wrote:
> >> To save the tabs, right click any one of them and select the "Select All
> >> Tabs" item. They will all highlight. Right click on one of them and
> >> select the "Bookmark Tabs" item. A
On 3/27/2023 8:37 PM, a a wrote:
I can select All Opened Tabs (as from the given link)
and get 1,000+ Opened Tabs ( I am afraid, this is s number of all saved
bookmarks in the past)
I go to menu, Bookmarks, Manage Boomarks and copy Tabs
and
On 3/27/2023 8:37 PM, a a wrote:
To save the tabs, right click any one of them and select the "Select All
Tabs" item. They will all highlight. Right click on one of them and
select the "Bookmark Tabs" item. A dialog box will open with an entry
lone for the Name to use (like "Tabset1") and a
On Tuesday, 28 March 2023 at 02:07:43 UTC+2, Thomas Passin wrote:
> On 3/27/2023 4:02 PM, Thomas Passin wrote:
> > On 3/27/2023 3:07 PM, a a wrote:
> >> On Monday, 27 March 2023 at 19:19:41 UTC+2, Thomas Passin wrote:
> >>> On 3/27/2023 10:07 AM, a a wrote:
> Ok, I know, I need to switch
On 3/27/2023 4:02 PM, Thomas Passin wrote:
On 3/27/2023 3:07 PM, a a wrote:
On Monday, 27 March 2023 at 19:19:41 UTC+2, Thomas Passin wrote:
On 3/27/2023 10:07 AM, a a wrote:
Ok, I know, I need to switch to Windows 10 run on another PC next to
me.
I need to learn how to copy and move every
On 3/27/2023 3:07 PM, a a wrote:
On Monday, 27 March 2023 at 19:19:41 UTC+2, Thomas Passin wrote:
On 3/27/2023 10:07 AM, a a wrote:
Ok, I know, I need to switch to Windows 10 run on another PC next to me.
I need to learn how to copy and move every web page opened in Firefox as a
reference to
On Monday, 27 March 2023 at 19:19:41 UTC+2, Thomas Passin wrote:
> On 3/27/2023 10:07 AM, a a wrote:
> > Ok, I know, I need to switch to Windows 10 run on another PC next to me.
> >
> > I need to learn how to copy and move every web page opened in Firefox as a
> > reference to social media, web
On 3/27/2023 10:07 AM, a a wrote:
Ok, I know, I need to switch to Windows 10 run on another PC next to me.
I need to learn how to copy and move every web page opened in Firefox as a
reference to social media, web sites for Python, chat and more (about 50 web
pages live opened
This sounds
On Thursday, 23 March 2023 at 22:15:10 UTC+1, Thomas Passin wrote:
> On 3/23/2023 3:38 PM, Mats Wichmann wrote:
> > On 3/23/23 09:48, Thomas Passin wrote:
> >
> >> I didn't realize that Christoph Gohlke is still maintaining this site.
> >
> > Unless the the last-changed stuff stopped working,
On 3/23/2023 3:38 PM, Mats Wichmann wrote:
On 3/23/23 09:48, Thomas Passin wrote:
I didn't realize that Christoph Gohlke is still maintaining this site.
Unless the the last-changed stuff stopped working, it's in a static state:
by Christoph Gohlke. Updated on 26 June 2022 at 07:27 UTC
I
On 3/23/23 09:48, Thomas Passin wrote:
I didn't realize that Christoph Gohlke is still maintaining this site.
Unless the the last-changed stuff stopped working, it's in a static state:
by Christoph Gohlke. Updated on 26 June 2022 at 07:27 UTC
--
On 3/18/2023 3:05 PM, Thomas Passin wrote:
downloaded and run HWiNFO and AVE not supported, not greened out
That's too bad; you may be out of luck. It's possible that someone
has compiled the .pyd library in such a way that it does not need the
instruction set extensions. I'm sorry but I
On 3/22/2023 8:09 AM, a a wrote:
On Saturday, 18 March 2023 at 20:12:22 UTC+1, Thomas Passin wrote:
On 3/17/2023 11:52 AM, a a wrote:
On Friday, 17 March 2023 at 16:32:53 UTC+1, a a wrote:
On Friday, 17 March 2023 at 16:03:14 UTC+1, Thomas Passin wrote:
On 3/16/2023 8:07 PM, a a wrote:
On Saturday, 18 March 2023 at 20:12:22 UTC+1, Thomas Passin wrote:
> On 3/17/2023 11:52 AM, a a wrote:
> > On Friday, 17 March 2023 at 16:32:53 UTC+1, a a wrote:
> >> On Friday, 17 March 2023 at 16:03:14 UTC+1, Thomas Passin wrote:
> >>> On 3/16/2023 8:07 PM, a a wrote:
> Crash report:
>
On 3/17/2023 11:52 AM, a a wrote:
On Friday, 17 March 2023 at 16:32:53 UTC+1, a a wrote:
On Friday, 17 March 2023 at 16:03:14 UTC+1, Thomas Passin wrote:
On 3/16/2023 8:07 PM, a a wrote:
Crash report:
Problem Caption:
Problem Event Name: APPCRASH
Application name: python.exe
Application
On 3/17/2023 11:32 AM, a a wrote:
On Friday, 17 March 2023 at 16:03:14 UTC+1, Thomas Passin wrote:
It would be worth trying to downgrade the multiarray version to an
earlier one and see if that fixes the problem.
Thank you Thomas for your kind reply.
I am fully aware to be living on an old
On Friday, 17 March 2023 at 16:03:14 UTC+1, Thomas Passin wrote:
> On 3/16/2023 8:07 PM, a a wrote:
> > Crash report:
> >
> > Problem Caption:
> > Problem Event Name: APPCRASH
> > Application name: python.exe
> > Application version: 3.8.7150.1013
> > Application time signature: 5fe0df5a
>
On Friday, 17 March 2023 at 16:03:14 UTC+1, Thomas Passin wrote:
> On 3/16/2023 8:07 PM, a a wrote:
> > Crash report:
> >
> > Problem Caption:
> > Problem Event Name: APPCRASH
> > Application name: python.exe
> > Application version: 3.8.7150.1013
> > Application time signature: 5fe0df5a
>
On Friday, 17 March 2023 at 16:32:53 UTC+1, a a wrote:
> On Friday, 17 March 2023 at 16:03:14 UTC+1, Thomas Passin wrote:
> > On 3/16/2023 8:07 PM, a a wrote:
> > > Crash report:
> > >
> > > Problem Caption:
> > > Problem Event Name: APPCRASH
> > > Application name: python.exe
> > >
On 3/16/2023 8:07 PM, a a wrote:
Crash report:
Problem Caption:
Problem Event Name: APPCRASH
Application name: python.exe
Application version: 3.8.7150.1013
Application time signature: 5fe0df5a
Error module name: _multiarray_umath.cp38-win32.pyd
Version of the module with
Crash report:
Problem Caption:
Problem Event Name: APPCRASH
Application name: python.exe
Application version: 3.8.7150.1013
Application time signature: 5fe0df5a
Error module name:_multiarray_umath.cp38-win32.pyd
Version of the module with the error: 0.0.0.0
Time signature
Irit Katriel added the comment:
This was reported for 3.6 and there was not enough information to figure out
what the problem is. I am closing it because it's unlikely that anyone will be
do anything about this unless it is reported again for a current Python
version, and with more
Alex Waygood added the comment:
Given that there has been no activity on this issue for over three years, I am
closing this as "rejected".
--
nosy: +AlexWaygood
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tracker
Steve Dower added the comment:
Unless someone can find an authoring bug under Tools/msi, I don't think we can
do anything about this. We rely on the built-in Windows support for adding and
removing these variables, and if that's broken, we can't do anything with our
current setup.
I really
1 - 100 of 1186 matches
Mail list logo
