On 17/09/2023 13.20, James Greenham via Python-list wrote:
Hello,
On the face of it, the Python-Mac mailing list is largely inactive so I'm
posting here since it looks like this one is livelier.
What happens when doGrab() is called from the REPL, after being 'fed'
data you expect is valid?
k which manifests by Python Launcher
popping up in Dock and is trying forever until I quit the launcher that
force-quits the widget showing the error icon.
The issue seems to originate in the doGrab handler (module or whatever the
correct Python term fits the definition) immediately following th
On 11/11/22, ohins...@gmail.com wrote:
>
> I am real a beginner of Python. Not able to create a Python launcher
> (shortcut) on Desktop after the installation.
Did you already install Python? If not, open the Store, and install
the Python 3.11 app that's published by the P
On 11/11/2022 4:44 PM, ohins...@gmail.com wrote:
Hello,
I am real a beginner of Python. Not able to create a Python launcher
(shortcut) on Desktop after the installation.
Would you kindly instruct how to do it?
Windows 11-Home, 64 bits, HP desktop
If you get an offer of Python
Hello,
I am real a beginner of Python. Not able to create a Python launcher
(shortcut) on Desktop after the installation.
Would you kindly instruct how to do it?
Windows 11-Home, 64 bits, HP desktop
Thanks,
Dan
--
https://mail.python.org/mailman/listinfo/python-list
Yes truly this exact question is a headache for beginners. Though it was
not for me.
On Thu, 16 Apr, 2020, 12:51 am Grant Edwards,
wrote:
> On 2020-04-15, Pieter van Oostrum wrote:
> > Angel V writes:
> >
> >> Hello,
> >>
> >> I'm new to Python and recently began to self learn the language.
>
On 2020-04-15, Pieter van Oostrum wrote:
> Angel V writes:
>
>> Hello,
>>
>> I'm new to Python and recently began to self learn the language.
>> Unfortunately, whenever I try to launch it, I'm met with a black pop-up
>> screen the disappears as soon as it comes up. I've tried uninstalling and I
>
Angel V writes:
> Hello,
>
> I'm new to Python and recently began to self learn the language.
> Unfortunately, whenever I try to launch it, I'm met with a black pop-up
> screen the disappears as soon as it comes up. I've tried uninstalling and I
> just run into the same issue. I tried downloading
What is the exact thing you are trying to launch?
On Wed, 15 Apr, 2020, 5:41 pm Angel V, wrote:
> Hello,
>
> I'm new to Python and recently began to self learn the language.
> Unfortunately, whenever I try to launch it, I'm met with a black pop-up
> screen the disappears as soon as it comes up.
Hello,
I'm new to Python and recently began to self learn the language.
Unfortunately, whenever I try to launch it, I'm met with a black pop-up
screen the disappears as soon as it comes up. I've tried uninstalling and I
just run into the same issue. I tried downloading the program onto my
brother'
On Tue, Jun 27, 2017 at 5:41 AM, Ben S. via Python-list
wrote:
>
> When I always call Python script from CommandPrompt like
>
> D:\tools\Python\python.exe mypythonscript.py
>
> then this Launcher should not be necessary.
The launcher implements shebang support for directly running Python
scripts
Double Post:
https://python-forum.io/Thread-Python-launcher-required-to-run-py-scripts-on-Windows
Pleas don't do this. It's not a nice behavior.
Thanks.
Andre
--
https://mail.python.org/mailman/listinfo/python-list
On Tuesday, June 27, 2017 at 1:41:22 AM UTC-4, Ben S. wrote:
> As I observed v3.6.1 installs (on Windows 7) in addition to the core python
> engine a second program "Python Launcher".
>
> As far as I read this component seems to be not necessary since it only aims
> t
On 6/27/2017 1:41 AM, Ben S. via Python-list wrote:
As I observed v3.6.1 installs (on Windows 7) in addition to the core python engine a
second program "Python Launcher".
As far as I read this component seems to be not necessary since it only aims to
facilitate the handling with *.
As I observed v3.6.1 installs (on Windows 7) in addition to the core python
engine a second program "Python Launcher".
As far as I read this component seems to be not necessary since it only aims to
facilitate the handling with *.py scripts on Windows.
When I always call Python s
On 1/10/2016 6:38 AM, Tim Golden wrote:
On 10/01/2016 05:18, Edward Diener wrote:
On 1/9/2016 11:03 AM, Tim Golden wrote:
On 06/01/2016 00:48, Edward Diener wrote:
The Python launcher in Windows is a neat tool for running multiple
versions of Python 2 and Python 3 at different times. It
On 1/10/2016 6:38 AM, Tim Golden wrote:
On 10/01/2016 05:18, Edward Diener wrote:
On 1/9/2016 11:03 AM, Tim Golden wrote:
On 06/01/2016 00:48, Edward Diener wrote:
The Python launcher in Windows is a neat tool for running multiple
versions of Python 2 and Python 3 at different times. It
On 10/01/2016 05:18, Edward Diener wrote:
On 1/9/2016 11:03 AM, Tim Golden wrote:
On 06/01/2016 00:48, Edward Diener wrote:
The Python launcher in Windows is a neat tool for running multiple
versions of Python 2 and Python 3 at different times. It allows as
options the ability to specify the
On 1/9/2016 11:03 AM, Tim Golden wrote:
On 06/01/2016 00:48, Edward Diener wrote:
The Python launcher in Windows is a neat tool for running multiple
versions of Python 2 and Python 3 at different times. It allows as
options the ability to specify the latest version of either Python 2 or
Python
On 06/01/2016 00:48, Edward Diener wrote:
The Python launcher in Windows is a neat tool for running multiple
versions of Python 2 and Python 3 at different times. It allows as
options the ability to specify the latest version of either Python 2 or
Python 3 defaulting to the 64-bit version if
The Python launcher in Windows is a neat tool for running multiple
versions of Python 2 and Python 3 at different times. It allows as
options the ability to specify the latest version of either Python 2 or
Python 3 defaulting to the 64-bit version if both exist, or a specific
32-bit or 64-bit
In a message of Sun, 13 Sep 2015 23:46:37 +0100, Mark Lawrence writes:
>Exactly the same thing happened when I upgraded to 3.5.0. so raised
>http://bugs.python.org/issue25089 just in case it hurts other people
>more than it hurts me.
>
>--
>My fellow Pythonistas, ask not what our language can d
On 10/09/2015 16:56, Mark Lawrence wrote:
On 10/09/2015 11:20, Tim Golden wrote:
On 10/09/2015 00:52, Mark Lawrence wrote:
I've installed 3.5 for all users so it's in C:\Program Files
From
https://docs.python.org/3.5/using/windows.html#from-the-command-line it
says "System-wide installations o
On 10/09/2015 11:20, Tim Golden wrote:
On 10/09/2015 00:52, Mark Lawrence wrote:
I've installed 3.5 for all users so it's in C:\Program Files
From
https://docs.python.org/3.5/using/windows.html#from-the-command-line it
says "System-wide installations of Python 3.3 and later will put the
launche
On 10/09/2015 00:52, Mark Lawrence wrote:
> I've installed 3.5 for all users so it's in C:\Program Files
>
> From
> https://docs.python.org/3.5/using/windows.html#from-the-command-line it
> says "System-wide installations of Python 3.3 and later will put the
> launcher on your PATH. The launcher i
I've installed 3.5 for all users so it's in C:\Program Files
From
https://docs.python.org/3.5/using/windows.html#from-the-command-line it
says "System-wide installations of Python 3.3 and later will put the
launcher on your PATH. The launcher is compatible with all available
versions of Pytho
Zachary Ware wrote:
On Jul 30, 2015 2:05 AM, "ElChino" mailto:elch...@cnn.cn>>
wrote:
>
> If I in a cmd-shell (actually it is 4NT), do:
> c:>py -3 -V & python3 -V
>
> I get:
> Requested Python version (3) not installed << ! from py -3 -V
> Python 3.5.0b2 << ! from the 2nd cmd.
On Jul 30, 2015 2:05 AM, "ElChino" wrote:
>
> If I in a cmd-shell (actually it is 4NT), do:
> c:>py -3 -V & python3 -V
>
> I get:
> Requested Python version (3) not installed << ! from py -3 -V
> Python 3.5.0b2 << ! from the 2nd cmd.
>
> What nonsense is this? I DO HAVE Python3 in my %PAT
On 7/30/2015 3:03 AM, ElChino wrote:
If I in a cmd-shell (actually it is 4NT), do:
c:>py -3 -V & python3 -V
I get:
Requested Python version (3) not installed << ! from py -3 -V
Python 3.5.0b2 << ! from the 2nd cmd.
What nonsense is this? I DO HAVE Python3 in my %PATH.
A Registry set
On 30/07/2015 08:03, ElChino wrote:
If I in a cmd-shell (actually it is 4NT), do:
c:>py -3 -V & python3 -V
I get:
Requested Python version (3) not installed << ! from py -3 -V
Python 3.5.0b2 << ! from the 2nd cmd.
What nonsense is this? I DO HAVE Python3 in my %PATH.
A Registry sett
ElChino wrote:
> If I in a cmd-shell (actually it is 4NT), do:
>c:>py -3 -V & python3 -V
>
> I get:
>Requested Python version (3) not installed << ! from py -3 -V
>Python 3.5.0b2 << ! from the 2nd cmd.
>
> What nonsense is this? I DO HAVE Python3 in my %PATH.
> A Registry setting
If I in a cmd-shell (actually it is 4NT), do:
c:>py -3 -V & python3 -V
I get:
Requested Python version (3) not installed << ! from py -3 -V
Python 3.5.0b2 << ! from the 2nd cmd.
What nonsense is this? I DO HAVE Python3 in my %PATH.
A Registry setting gone haywire?
--
https://mail.python
Am 01.02.2013 00:59, schrieb Vinay Sajip:
Thomas Heller ctypes.org> writes:
What I meant to write is this:
when the shebang line in script.py contains this:
#!/usr/bin/python3.1-32
then emacs SHOULD run
py.exe -3.1-32 script.py
and the launcher runs
c:\Python31\python.exe script.p
Thomas Heller ctypes.org> writes:
> What I meant to write is this:
>
> when the shebang line in script.py contains this:
>#!/usr/bin/python3.1-32
> then emacs SHOULD run
>py.exe -3.1-32 script.py
> and the launcher runs
>c:\Python31\python.exe script.py
IMO it would be better for em
Am 31.01.2013 17:35, schrieb Thomas Heller:
Am 31.01.2013 12:05, schrieb Andreas Röhler:
Am 31.01.2013 10:03, schrieb Thomas Heller:
Has someone managed to patch python-mode.el to use
the PEP 397 python launcher when you hit C-c C-c?
It seems that emacs should parse the shebang line in the
Am 31.01.2013 12:05, schrieb Andreas Röhler:
Am 31.01.2013 10:03, schrieb Thomas Heller:
Has someone managed to patch python-mode.el to use
the PEP 397 python launcher when you hit C-c C-c?
It seems that emacs should parse the shebang line in the edited
python script and pass the corresponding
Am 31.01.2013 10:03, schrieb Thomas Heller:
Has someone managed to patch python-mode.el to use
the PEP 397 python launcher when you hit C-c C-c?
It seems that emacs should parse the shebang line in the edited
python script and pass the corresponding arguments to py.exe.
Yes, that's th
Has someone managed to patch python-mode.el to use
the PEP 397 python launcher when you hit C-c C-c?
It seems that emacs should parse the shebang line in the edited
python script and pass the corresponding arguments to py.exe.
Thomas
--
http://mail.python.org/mailman/listinfo/python-list
On 27/06/12 22:45:47, David Thomas wrote:
> Thank you ever so much raw_input works fine.
> Do you think I should stick with Python 2 before I go to 3?
I think so. The differences are not that big, but big
enough to confuse a beginner. Once you know pyhton2,
read http://docs.python.org/py3k/what
Thank you ever so much raw_input works fine. Do you think I should stick with
Python 2 before I go to 3?
I have a text book which is using 3 but I've been using an online tutorial
which has been helping me lots, which uses version 2.
I found by just typing python then having a space and dragging
On 27/06/12 19:05:44, David Thomas wrote:
> Is this why I keep getting an error using launcher?
No.
Yesterday your problem was that you tried this:
input("\n\nPress the enter key to exit")
That works fine in Pyhton3, but you are using python2
and in python2, the you must do this instead:
On Tuesday, June 26, 2012 10:48:22 PM UTC+1, Hans Mulder wrote:
> On 26/06/12 22:41:59, Dave Angel wrote:
> > On 06/26/2012 03:16 PM, Hans Mulder wrote:
> >>
> >>
> >> Python is an executable, and is
> >> typically located in a "bin" directory. To find out where
> >> it is, type
> >>
> >> ty
On 06/26/2012 05:48 PM, Hans Mulder wrote:
> On 26/06/12 22:41:59, Dave Angel wrote:
>
> No, I meant: $ type python python is
> /Library/Frameworks/Python.framework/Versions/2.7/bin/python 'type' is
> a bash builtin that tells you how bash would interpret a command.
> 'which' is a separate progra
On 26/06/2012 23:35, Dennis Lee Bieber wrote:
(And, on Windows at least, #! lines don't do
anything)
New for Python 3.3 http://www.python.org/dev/peps/pep-0397/
--
Cheers.
Mark Lawrence.
--
http://mail.python.org/mailman/listinfo/python-list
On 26/06/12 22:41:59, Dave Angel wrote:
> On 06/26/2012 03:16 PM, Hans Mulder wrote:
>>
>>
>> Python is an executable, and is
>> typically located in a "bin" directory. To find out where
>> it is, type
>>
>> type python
>>
>> at the shell prompt (that's the first prompt you get if you
>> ope
On 06/26/2012 03:16 PM, Hans Mulder wrote:
>
>
> Python is an executable, and is
> typically located in a "bin" directory. To find out where
> it is, type
>
> type python
>
> at the shell prompt (that's the first prompt you get if you
> open a Terminal window).
>
>
That's a typo. You presu
On 26/06/12 21:51:41, Dennis Lee Bieber wrote:
> On Tue, 26 Jun 2012 10:19:45 -0700 (PDT), David Thomas
> declaimed the following in gmane.comp.python.general:
>
>
>> http://www.freeimagehosting.net/ilbqt
>
> That's an interesting configuration...
>
> "pythonw.exe" is a version of
On 26/06/12 20:11:51, David Thomas wrote:
> On Monday, June 25, 2012 7:19:54 PM UTC+1, David Thomas wrote:
>> Hello,
>> This is my first post so go easy on me. I am just beginning to program
>> using Python on Mac. When I try to execute a file using Python Launcher my
>
On Tue, Jun 26, 2012 at 10:19 AM, David Thomas wrote:
> I have installed Python 2.7.3 from Python.org also in Terminal it states that
> I have 2.7.3.
> How can I execute the script from Terminal? I've tried typing python into
> the window and then dragging the file to terminal but I get a synta
On Monday, June 25, 2012 7:19:54 PM UTC+1, David Thomas wrote:
> Hello,
> This is my first post so go easy on me. I am just beginning to program using
> Python on Mac. When I try to execute a file using Python Launcher my code
> seems to cause an error in terminal, when I execu
(You forgot to include the list on this message, but I'm including them
in my reply)
On 06/26/2012 02:07 PM, David Thomas wrote:
>
>
> On Tuesday, June 26, 2012 6:37:42 PM UTC+1, Dave Angel wrote:
>>
>> On 06/26/2012 01:19 PM, David Thomas wrote:
>>> I have installed Python 2.7.3 from Python.or
On Tuesday, June 26, 2012 6:37:42 PM UTC+1, Dave Angel wrote:
> On 06/26/2012 01:19 PM, David Thomas wrote:
> > I have installed Python 2.7.3 from Python.org also in Terminal it states
> > that I have 2.7.3.
> > How can I execute the script from Terminal? I've tried typing python into
> > the wi
On 06/26/2012 01:19 PM, David Thomas wrote:
> I have installed Python 2.7.3 from Python.org also in Terminal it states that
> I have 2.7.3.
> How can I execute the script from Terminal? I've tried typing python into
> the window and then dragging the file to terminal but I get a syntax error.
so go easy on me. I am just beginning to program
> > using Python on Mac. When I try to execute a file using Python Launcher my
> > code seems to cause an error in terminal, when I execute the exact same
> > piece of code and run it in windows it seems to execute as exactly i
On Mon, Jun 25, 2012 at 11:19 AM, David Thomas wrote:
> Hello,
> This is my first post so go easy on me. I am just beginning to program using
> Python on Mac. When I try to execute a file using Python Launcher my code
> seems to cause an error in terminal, when I execute the exac
Hello,
This is my first post so go easy on me. I am just beginning to program using
Python on Mac. When I try to execute a file using Python Launcher my code
seems to cause an error in terminal, when I execute the exact same piece of
code and run it in windows it seems to execute as exactly
t; as one would expect ... but not using the Python launcher
> > either directly or indirectly (by double clicking on a Python icon).
> > Has anyone else observed this and, more importantly, found a fix for
> > this problem?
>
> > André
I can launch a script from IDLE
t; as one would expect ... but not using the Python launcher
> > either directly or indirectly (by double clicking on a Python icon).
> > Has anyone else observed this and, more importantly, found a fix for
> > this problem?
>
> > André
>
> My guess is the e
On Nov 3, 7:57 am, André <[EMAIL PROTECTED]> wrote:
> I just installed Leopard on my Mac. I already was using Python 2.5.
> I can run a Python script from a terminal window by typing "python
> script.py" as one would expect ... but not using the Python launcher
> eithe
I just installed Leopard on my Mac. I already was using Python 2.5.
I can run a Python script from a terminal window by typing "python
script.py" as one would expect ... but not using the Python launcher
either directly or indirectly (by double clicking on a Python icon).
Has anyone els
60 matches
Mail list logo
