Lawrence D'Oliveiro wrote:
You mean “GUI console”. So non-GUI apps get a GUI element whether they want
it or not, while GUI ones don’t. That’s completely backwards.
The G in GUI stands for Graphical. I wouldn't call a window that
displays nothing but text graphical.
--
Greg
--
gb345 wrote:
I see how clicking directly on these files would obviate the need
to specify the path of the interpreter, but it's still not clear
to me how the interpreter would know where to look for the myscript.py
module that both the GUI scripts require.
If it's in the same directory as the
In message 8ivfa3fif...@mid.individual.net, Gregory Ewing wrote:
Lawrence D'Oliveiro wrote:
You mean “GUI console”. So non-GUI apps get a GUI element whether they
want it or not, while GUI ones don’t. That’s completely backwards.
The G in GUI stands for Graphical. I wouldn't call a window
In message mailman.311.1288232442.2218.python-l...@python.org, Dave Angel
wrote:
Gee, maybe when you're trying to track down problems, you might try
starting the application in a console?
On a rationally-designed OS, I have a choice. I can do that, but that’s not
really my first resort: the
On Thu, 28 Oct 2010 12:54:03 +1300, Lawrence D'Oliveiro wrote:
Why would you want both CLI and GUI functions in one program?
An obvious example was the one which was being discussed, i.e. the Python
interpreter.
But the Python interpreter has no GUI.
It may have one if you use wx,
On 2:59 PM, Lawrence D'Oliveiro wrote:
In messagepan.2010.10.26.17.38.14.766...@nowhere.com, Nobody wrote:
python.exe is a console executable, pythonw.exe is a GUI executable. Hence
python.exe automatically gets a console window, while pythonw.exe doesn't.
That's the whole reason why Windows
In message mailman.296.1288167734.2218.python-l...@python.org, Dave Angel
wrote:
On 2:59 PM, Lawrence D'Oliveiro wrote:
In messagepan.2010.10.26.17.38.14.766...@nowhere.com, Nobody wrote:
python.exe is a console executable, pythonw.exe is a GUI executable.
Hence python.exe automatically
In message pan.2010.10.27.01.12.21.766...@nowhere.com, Nobody wrote:
On Wed, 27 Oct 2010 13:46:28 +1300, Lawrence D'Oliveiro wrote:
Why would you want both CLI and GUI functions in one program?
An obvious example was the one which was being discussed, i.e. the Python
interpreter.
But the
On 2:59 PM, Lawrence D'Oliveiro wrote:
In messagemailman.296.1288167734.2218.python-l...@python.org, Dave Angel
wrote:
On 2:59 PM, Lawrence D'Oliveiro wrote:
In messagepan.2010.10.26.17.38.14.766...@nowhere.com, Nobody wrote:
python.exe is a console executable, pythonw.exe is a GUI
In message mailman.208.1287970911.2218.python-l...@python.org, MRAB wrote:
On 25/10/2010 02:19, Lawrence D'Oliveiro wrote:
In messagemailman.187.1287916654.2218.python-l...@python.org, Dave
Angel wrote:
No. GUI programs are marked as win-app, so w stands for Windows. Non
GUI programs run
In message mailman.216.1287980107.2218.python-l...@python.org, Steve
Holden wrote:
and, in fact, the console is only a GUI window in a windowed system. It
might be one of the console emulation windows that init starts under
linux, or even a terminal connected to a computer by a serila line,
On 10/26/2010 2:08 AM, Lawrence D'Oliveiro wrote:
In message mailman.208.1287970911.2218.python-l...@python.org, MRAB wrote:
On 25/10/2010 02:19, Lawrence D'Oliveiro wrote:
In messagemailman.187.1287916654.2218.python-l...@python.org, Dave
Angel wrote:
No. GUI programs are marked as
On Tue, 26 Oct 2010 02:38:43 -0400, Steve Holden wrote:
I really don't understand what you are trying to say here. Could you
please explain? I know you to be a capable and sensible person, but this
sounds like nonsense to me, so I must be misunderstanding.
I think he's saying that on a
On 2010-10-26, Lawrence D'Oliveiro l...@geek-central.gen.new_zealand wrote:
In message mailman.216.1287980107.2218.python-l...@python.org, Steve
Holden wrote:
and, in fact, the console is only a GUI window in a windowed system. It
might be one of the console emulation windows that init
On Tue, 26 Oct 2010 14:44:11 +, Grant Edwards wrote:
There is no difference based on the name of your executable, how it
is built, or what libraries it links to; the only difference is in
its run-time behaviour, whether it invokes any GUI functions or not.
No, we're not talking about
In message pan.2010.10.26.17.38.14.766...@nowhere.com, Nobody wrote:
python.exe is a console executable, pythonw.exe is a GUI executable. Hence
python.exe automatically gets a console window, while pythonw.exe doesn't.
That's the whole reason why Windows has separate python.exe and
In message mailman.265.1288113240.2218.python-l...@python.org, Dennis Lee
Bieber wrote:
(The Amiga made it simple -- a shell invocation received a non-zero
argc, with command line parameters in argv; a clicked invocation
received argc of 0, and argv pointed to a structure containing the
On Wed, 27 Oct 2010 13:46:28 +1300, Lawrence D'Oliveiro wrote:
Why would you want both CLI and GUI functions in one program?
An obvious example was the one which was being discussed, i.e. the Python
interpreter. Depending upon the script, it may need to behave as a
command-line utility (read
On 2:59 PM, Lawrence D'Oliveiro wrote:
In message
mailman.154.1287832721.2218.python-l...@python.org, Dave Angel wrote:
Presumably the original pythonw.exe was called that because it's marked
as a windows-app. In win-speak, that means it has a gui. Applications
that are not so-marked are
In message mailman.187.1287916654.2218.python-l...@python.org, Dave Angel
wrote:
On 2:59 PM, Lawrence D'Oliveiro wrote:
In message
mailman.154.1287832721.2218.python-l...@python.org, Dave Angel wrote:
Presumably the original pythonw.exe was called that because it's marked
as a
On 25/10/2010 02:19, Lawrence D'Oliveiro wrote:
In messagemailman.187.1287916654.2218.python-l...@python.org, Dave Angel
wrote:
On 2:59 PM, Lawrence D'Oliveiro wrote:
In message
mailman.154.1287832721.2218.python-l...@python.org, Dave Angel wrote:
Presumably the original pythonw.exe was
On 10/24/2010 9:40 PM, MRAB wrote:
On 25/10/2010 02:19, Lawrence D'Oliveiro wrote:
In messagemailman.187.1287916654.2218.python-l...@python.org, Dave
Angel
wrote:
On 2:59 PM, Lawrence D'Oliveiro wrote:
In message
mailman.154.1287832721.2218.python-l...@python.org, Dave Angel wrote:
In message mailman.128.1287758336.2218.python-l...@python.org, Tim Golden
wrote:
If you were to rename the .py to a .pyw it would run without a console
window showing up.
Presumably the “w” stands for “window”. Wouldn’t it be less confusing if it
was the other way round?
--
On Sat, Oct 23, 2010 at 12:32 AM, Lawrence D'Oliveiro
l...@geek-central.gen.new_zealand wrote:
In message mailman.128.1287758336.2218.python-l...@python.org, Tim Golden
wrote:
If you were to rename the .py to a .pyw it would run without a console
window showing up.
Presumably the “w” stands
In message mailman.150.1287821953.2218.python-l...@python.org, Chris
Rebert wrote:
On Sat, Oct 23, 2010 at 12:32 AM, Lawrence D'Oliveiro
l...@geek-central.gen.new_zealand wrote:
In message mailman.128.1287758336.2218.python-l...@python.org, Tim
Golden wrote:
If you were to rename the .py
On 2:59 PM, Lawrence D'Oliveiro wrote:
In messagemailman.128.1287758336.2218.python-l...@python.org, Tim Golden
wrote:
If you were to rename the .py to a .pyw it would run without a console
window showing up.
Presumably the “w” stands for “window”. Wouldn’t it be less confusing if it
was
In message
mailman.154.1287832721.2218.python-l...@python.org, Dave Angel wrote:
Presumably the original pythonw.exe was called that because it's marked
as a windows-app. In win-speak, that means it has a gui. Applications
that are not so-marked are console-apps, and get a console created if
In i9n9ed$q0...@reader1.panix.com gb345 gb...@invalid.com writes:
I have a handy Python script, which takes a few command-line
arguments, and accepts a few options. I developed it on Unix, with
very much of a Unix-mindset. Some Windows-using colleagues have
asked me to make the script easy to
On 22/10/2010 15:25, gb345 wrote:
3. Both versions of the app work fine on Windows 7, as long as
I do the following:
a. run CMD
b. cd to where the GUI script and my original script live
c. execute either
C:\Python27\python myapp_tk.py
or
C:\Python27\python
In mailman.128.1287758336.2218.python-l...@python.org Tim Golden
m...@timgolden.me.uk writes:
On 22/10/2010 15:25, gb345 wrote:
3. Both versions of the app work fine on Windows 7, as long as
I do the following:
a. run CMD
b. cd to where the GUI script and my original script live
gb345 wrote:
In mailman.128.1287758336.2218.python-l...@python.org Tim Golden
m...@timgolden.me.uk writes:
On 22/10/2010 15:25, gb345 wrote:
3. Both versions of the app work fine on Windows 7, as long as
I do the following:
a. run CMD
b. cd to where the GUI script and my original
I much prefer the wx version of the GUI over the tk version of my app.
Check out Python 2.7's Tkinter support for Tile. The enhanced version of
Tkinter that ships with 2.7 supports native OS themes across all
platforms giving you very professional looking user interfaces.
wx has lots more
32 matches
Mail list logo
