Unix-head needs to Windows-ize his Python script (II)

Lawrence D'Oliveiro ldo at geek-central.gen.new_zealand
Wed Oct 27 01:47:56 CEST 2010


In message <pan.2010.10.26.17.38.14.766000 at 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
> pythonw.exe programs, while Unix can use a single /usr/bin/python program
> for both GUI and console usage.
> 
> The Windows approach makes it easier to Do The Right Thing automatically
> ...

Except it provides no easy way to capture the contents of that “console”, 
for when you’re trying to track down problems, because it disappears as soon 
as the program exits.

It would be a stretch indeed to call this “doing the right thing”, 
automatically or otherwise.



More information about the Python-list mailing list