Henry S. Thompson wrote:
> Some approach to support future-proofing in general would seem to be in
> order.
> Given some other precedents, adding a boolean argument called either 'strict'
> or 'lax' would be my preference.
An alternative would be to refactor urllib.parse to use strategy objects
Schimon Jehudah writes:
> Is there an "ignore" option for "urljoin" to allow schemes that are not
> included in the registry of the interpreter of the Python computer
> language?
Some approach to support future-proofing in general would seem to be
in order. Given some other precedents, adding a
Is there an "ignore" option for "urljoin" to allow schemes that are not
included in the registry of the interpreter of the Python computer
language?
I think that it is needed to have, even if it is not registered, as
there are ongoing attempts to try to censor Gemini and Gopher.
gemini://woodpeck
Schimon Jehudah via Python-list writes:
> Yesterday, I have added support for a new syndication format, Gemini
> feed.
I note that 'gemini' is not (yet?) a registered URI scheme:
https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml
ht
--
Henry S. Thompson, School of Informat
Good day.
Yesterday, I have added support for a new syndication format, Gemini
feed.
Yet, it appears that module urljoin fails at its task, even though
module urlsplit correctly handles Gemini.
Python 3.13.3
>>> from urllib.parse import urljoin
>>> urljoin('gopher://gopher.floodgap.com:70/1/ove
to use.
Each release adds more symbols to the limited API.
So if you compile against 3.10 version it works with 3.10, 3.11, 3.12 etc,
but not with 3.9.
My pycxx project has test code that I use to verify pycxx’s use of python API.
You could check out the source and run my tests to see how things
It sounds weird that symbols from Limited API are _missing_ (I'd
expect them to be there no matter what library version you link with).
But, I haven't done this myself, so, what do I know? It would help
though to see the actual error.
That aside: why do you want to do this? One side effect of doi
without the -lpython and it should
just work.
Barry
>
> Le ven. 29 mars 2024 à 10:10, Barry a écrit :
>>
>>
>>
>>> On 28 Mar 2024, at 16:13, Olivier B. via Python-list
>>> wrote:
>>>
>>> But on Linux, it seems that linking to
It is not a symlink on my system, where i built python myself, but a
15KB so file. But it seems to lack lots of python symbols.
Maybe what i should do is actually make libpython.so a physical copy
of libpyton311.so before linking to it, so now on any system the
module would look to load libpython.
> On 28 Mar 2024, at 16:13, Olivier B. via Python-list
> wrote:
>
> But on Linux, it seems that linking to libpython3.so instead of
> libpython3.11.so.1.0 does not have the same effect, and results in
> many unresolved python symbols at link time
>
> Is this functionality only available on W
I have a python module that includes some C++ code that links with the
Python C API
I have now modified the c++ code so that it only uses the Limited API,
and linked with python3.lib instead of python311.lib.
I can now use that python module with different python versions on Windows
But on Linux
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 Wi
find it in settings you can turn off
the python and python3 aliases.
Thank you! That did it. These two settings were off in the older Windows
10 installation and on in the new Windows 11. Changed there and the
shebang lines with "/env" work as expected.
I didn't remember ev
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 pytho
> 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 p
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 distri
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 t
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 like
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
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, 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
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
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 a
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
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, using either the latest Python or one
version before (depending on av
4 23:59 (GMT+10:00) 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
w
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 think of is that "python" may be defaulting to mean
python 2.
If you use "#!/usr/bin/env pyt
;/env" from my shebang lines, even if I don't
understand what's happening.
Thanks for the details.
Only thing I can think of is that "python" may be defaulting to mean
python 2.
If you use "#!/usr/bin/env python3" it may work on both.
No, it doesn't. T
derstand what's
happening.
Thanks for the details.
Only thing I can think of is that "python" may be defaulting to mean python 2.
If you use "#!/usr/bin/env python3" it may work on both.
No, it doesn't. That's the form I started with. When it didn't work I
thoug
Thanks for the details.
Only thing I can think of is that "python" may be defaulting to mean python 2.
If you use "#!/usr/bin/env python3" it may work on both.
Did you creates a py.ini file to configure py.exe?
See if you have %userappdata%\py.ini on either windows 10 or windows
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'
> 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 an
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 cr
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
version
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
Python.f
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 i
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 in the documentation.
The sheb
ssible download 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 li
'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 in the documentation.
Happy
> 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 / Py
he 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
--
https://mail.python.org/mailman/listinfo/python-list
ich part of the above you strongly disagree with. I might
> seem a bit OTT with "You cannot trust Microsoft" but I did put it in a
> specific context.
>
> PSF does try to make Python work identically in all operating systems it
> supports. The OP was using py.exe w
their
aforementioned strategy of locking in users to Windows.
I strongly disagree with this.
Not sure which part of the above you strongly disagree with. I might
seem a bit OTT with "You cannot trust Microsoft" but I did put it in a
specific context.
PSF does try to make P
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 i
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 Windo
ython-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
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
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 inter
the 1980s. They make their environment just different enough
to force users to invest brainspace to make it work and thereby lock-in their
users with their own muscle-memory. Very subtle. Not.
2. Installing Python in Microsoft's preferred location wasn't always
"standard
> 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
py
hould, according to your shebang, just like on Unix.
>
> Does that work with virtualenv or conda? I'm slowly getting up to speed
> with those.
I don't know. I imagine py is aware of venv if you run it from the
command line within the activated venv. But I doubt it is if you
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
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 launche
> 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 version
mething else, you get
something else. If you specify "/usr/bin/env python3", you get whatever
the user has in their PATH first.
> and that often is not what you want. OTOH you don't want to go
> symlinking python3 to some other version of python because then the OS
> syste
your Python executable.
Yes if you associate .py or .pyw with python.exe (or pythonw.exe), then
things work as you describe. However it's no longer recommended to do
that.
Instead---and I think this is the default now when you install
python---you should associate both .py and .pyw files wit
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 understand
y or .pyw with python.exe (or pythonw.exe), then
things work as you describe. However it's no longer recommended to do
that.
Instead---and I think this is the default now when you install
python---you should associate both .py and .pyw files with the py
launcher (py.exe) and it will examine th
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 la
> 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
--
h
n 3.11.5. Reading
the Python documentation it seems my shebang lines should work as before
- but they don't. The error message:
"Unable to create process using 'C:\usr\bin\env\python
"C:\Eigen\Src\launcher_versuche.py" ': Das System kann die angegebene
Datei nicht fin
put('Leave with Enter')" at the end.
Now I've got a new computer with Windows 11 and I've installed Python
3.12.1. On my older machine it's Windows 10 and Python 3.11.5. Reading
the Python documentation it seems my shebang lines should work as before
- but they don
> 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
--
https://mail.python.org/mailman/listinfo/python-li
> 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
GUI or for scripts with
something like "input('Leave with Enter')" at the end.
Now I've got a new computer with Windows 11 and I've installed Python
3.12.1. On my older machine it's Windows 10 and Python 3.11.5. Reading
the Python documentation it seems my shebang
or using WIN+r; the two last variants for GUI or for scripts with
> something like "input('Leave with Enter')" at the end.
>
> Now I've got a new computer with Windows 11 and I've installed Python
> 3.12.1. On my older machine it's Windows 10 and Py
;ve got a new computer with Windows 11 and I've installed Python
3.12.1. On my older machine it's Windows 10 and Python 3.11.5. Reading
the Python documentation it seems my shebang lines should work as before
- but they don't. The error message:
"Unable to create process using &#
Thanks, I'll look into it.
On Thu, 15 Jun 2023 at 10:25, Alan Gauld wrote:
> On 15/06/2023 08:58, Real Live FootBall Tv via Python-list wrote:
> > I have followed the instructions given on how to install the app. What I
> > needed was an application to cut of silence from my video and I saw auto
On 15/06/2023 08:58, Real Live FootBall Tv via Python-list wrote:
> I have followed the instructions given on how to install the app. What I
> needed was an application to cut of silence from my video and I saw auto
> editor demonstrated as one of the applications that could do that. It does
> cut
properly.
>
> It sounds like someone messed up an installation, perhaps of other
> programs like an editor and some unspecified thing does not work. I suggest
> they start over and be careful so that if some specific version of Python
> is needed, it gets installed in the right place and
unspecified thing does not work. I suggest they start
over and be careful so that if some specific version of Python is needed, it
gets installed in the right place and so on. We here cannot be expected to have
much idea about programs that perhaps we do not use.
Python can be used to build an editor
On 6/13/2023 9:43 PM, gene heskett via Python-list wrote:
On 6/13/23 19:10, Thomas Passin via Python-list wrote:
On 6/13/2023 5:32 PM, Alan Gauld via Python-list wrote:
Okay thanks. Meanwhile, I am not tech savvy so I may not say much here.
I followed all the commands as given on the website to
On 6/13/23 19:10, Thomas Passin via Python-list wrote:
On 6/13/2023 5:32 PM, Alan Gauld via Python-list wrote:
Okay thanks. Meanwhile, I am not tech savvy so I may not say much here.
I followed all the commands as given on the website to install auto
editor standing it on python but after render
On 6/13/2023 5:32 PM, Alan Gauld via Python-list wrote:
Okay thanks. Meanwhile, I am not tech savvy so I may not say much here.
I followed all the commands as given on the website to install auto
editor standing it on python but after rendering the XML file, I
couldn't open it with my Davinci Res
application, A
VIDEO
> EDITING APP, Auto EDITOR but it didn't work for some reasons
unknown to me.
You need to define "didn't work"
Did it work as a python interpreter?
ie. Did you get a >>> prompt in a terminal?
and without involvement f
On 12/06/2023 10:26, Real Live FootBall Tv via Python-list wrote:
> I did it because I was going to use it with another application, A VIDEO
> EDITING APP, Auto EDITOR but it didn't work for some reasons unknown to me.
You need to define "didn't work"
Did it work a
On 6/12/2023 5:26 AM, Real Live FootBall Tv via Python-list wrote:
I recently Installed and Uninstalled Python, hence the system was trying
to get why I UNINSTALLED python.
I did it because I was going to use it with another application, A VIDEO
EDITING APP, Auto EDITOR but it didn't wor
I recently Installed and Uninstalled Python, hence the system was trying
to get why I UNINSTALLED python.
I did it because I was going to use it with another application, A VIDEO
EDITING APP, Auto EDITOR but it didn't work for some reasons unknown to me.
Seeing, therefore, that the app d
On 2023-03-19, Greg Ewing wrote:
> On 20/03/23 7:07 am, Jon Ribbens wrote:
>> Ah, apparently it got removed in Python 3, which is a bit odd as the
>> last I heard it was added in Python 2.2 in order to achieve consistency
>> with other types.
>
> As far as I remember, the file type came into exist
On 2023-03-19, Stefan Ram wrote:
> Jon Ribbens writes:
>>(Also, I too find it annoying to have to avoid, but calling a local
>>variable 'file' is somewhat suspect since it shadows the builtin.)
>
> Thanks for your remarks, but I'm not aware
> of such a predefined name "file"!
Ah, apparently
On 2023-03-19, Stefan Ram wrote:
> Peng Yu writes:
>>But when I try the following code, get_body() is not found. How to get
>>get_body() to work?
>
> Did you know that this post of mine here was posted to
> Usenet with a Python script I wrote?
>
> That Python
On 20/03/23 7:07 am, Jon Ribbens wrote:
Ah, apparently it got removed in Python 3, which is a bit odd as the
last I heard it was added in Python 2.2 in order to achieve consistency
with other types.
As far as I remember, the file type came into existence
with type/class unification, and "open"
parts(), and
walk()."
But when I try the following code, get_body() is not found. How to get
get_body() to work?
$ python3 -c 'import email, sys; msg =
email.message_from_string(sys.stdin.read()); print(msg.get_body())'
<<< some_text
Traceback (most recent call last):
File &
following code, get_body() is not found. How to get
get_body() to work?
$ python3 -c 'import email, sys; msg =
email.message_from_string(sys.stdin.read()); print(msg.get_body())'
<<< some_text
Traceback (most recent call last):
File "", line 1, in
AttributeE
Roel Schroeven wrote:
> Chris Green schreef op 4/02/2023 om 16:17:
> > I am using Image from PIL and I'm getting a deprecation warning as
> > follows:-
> >
> > /home/chris/bin/picShrink.py:80: DeprecationWarning: ANTIALIAS is
> > deprecated
> and will be removed in Pillow 10 (2023-07-01). Use Re
Chris Green schreef op 4/02/2023 om 16:17:
I am using Image from PIL and I'm getting a deprecation warning as
follows:-
/home/chris/bin/picShrink.py:80: DeprecationWarning: ANTIALIAS is deprecated
and will be removed in Pillow 10 (2023-07-01). Use Resampling.LANCZOS instead.
But if I change l
On Sun, 5 Feb 2023 at 07:52, Chris Green wrote:
>
> I am using Image from PIL and I'm getting a deprecation warning as
> follows:-
>
> /home/chris/bin/picShrink.py:80: DeprecationWarning: ANTIALIAS is deprecated
> and will be removed in Pillow 10 (2023-07-01). Use Resampling.LANCZOS instead.
>
>
I am using Image from PIL and I'm getting a deprecation warning as
follows:-
/home/chris/bin/picShrink.py:80: DeprecationWarning: ANTIALIAS is deprecated
and will be removed in Pillow 10 (2023-07-01). Use Resampling.LANCZOS instead.
The code is very simple:-
...
...
from PIL import
, line 1, in
> > ImportError: DLL load failed while importing _tkinter: Das angegebene
> > Modul wurde nicht gefunden.
>
> How can I fix this and make it work?
>
Have a look at
https://stackoverflow.com/questions/25905540/importerror-no-module-named-tkinter
.
Most of the answers are for Linux/Mac, but there are Windows answers there,
too.
--
https://mail.python.org/mailman/listinfo/python-list
> On 23 Nov 2022, at 06:31, Stefan Ram wrote:
>
> darkst...@o2online.de writes:
>> I want learn python for 4 weeks and have problems, installing Tkinter. If I=
>> installed 3.11.0 for my windows 8.1 from python.org and type
>
> Ok, so you already installed from python.org. I wonder a
> littl
> On 22 Nov 2022, at 16:09, r...@zedat.fu-berlin.de wrote:
>
> darkst...@o2online.de writes:
>>> ImportError: DLL load failed while importing _tkinter: Das angegebene
>>> Modul wurde nicht gefunden.
>
> If you have not already done so, make sure that you install
> Python from python.org.
>
On 11/21/22 14:41, Thomas Passin wrote:
On 11/21/2022 1:24 PM, Stefan Ram wrote:
darkst...@o2online.de writes:
import _tkinter
I don't know why you get this error message. Here, I do not
get an error message from that line. However, the normal way
to use tkinter, as far as I know, is
; File "", line 1, in
> ImportError: DLL load failed while importing _tkinter: Das angegebene
> Modul wurde nicht gefunden.
How can I fix this and make it work?
When installing Python 3.11.0 did you check the box "tcl/tk and IDLE"?
(it's an option on the
ompilation settings or runtime
support versions that doesn't work with the OP's version of Python 8.1.
Or, since Python itself seems to be running, maybe the way the tkinter
binary was compiled isn't compatible even though Python 3.11 itself is.
Maybe this is a bug waiting to
ed while importing _tkinter: Das angegebene
> Modul wurde nicht gefunden.
How can I fix this and make it work?
--
https://mail.python.org/mailman/listinfo/python-list
” . “Command Prompt “
is out.
The picture is attached.
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Python-list on
behalf of Mats Wichmann
Sent: Wednesday, August 24, 2022 8:22:42 AM
To: python-list@python.org
Subject: Re: INSTALLATION DOES NOT WORK FRO G
On 8/23/22 05:00, Gladstone Rose wrote:
> Why is my installation of Python does not work at the command line for git
> bash.
>
> I get the following message
> bash: python3: command not found
The git bash package for Windows is built from msys2, a GNU/Linux type
environmen
On 23/08/2022 13.00, Gladstone Rose wrote:
Why is my installation of Python does not work at the command line for git bash.
I get the following message
bash: python3: command not found
It can be that you need to use python.exe instead of python3.exe, see my
work computers response when
Why is my installation of Python does not work at the command line for git bash.
I get the following message
bash: python3: command not found
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
--
https://mail.python.org/mailman/listinfo/python-list
1 - 100 of 2495 matches
Mail list logo
