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

[Steve Holden]

On 10/24/2010 9:40 PM, MRAB wrote:
> On 25/10/2010 02:19, Lawrence D'Oliveiro wrote:
>> In message<mailman.187.1287916654.2218.python-list at python.org>, Dave
>> Angel
>> wrote:
>>
>>> On 2:59 PM, Lawrence D'Oliveiro wrote:
>>>>
>>>> In message
>>>> <mailman.154.1287832721.2218.python-list at 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
>>>>> they weren't already started from one. That's where
>>>>> stdin/stdout/stderr
>>>>> get pointed.
>>>>
>>>> Which is completely backwards, isn’t it?
>>>>
>>> No. GUI programs are marked as win-app, so w stands for "Windows". Non
>>> GUI programs run in the console.
>>
>> 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.
> 
> No, it's not. The fact that the console is also a GUI window is an
> implementation detail: it happens to be displayed within a GUI
> environment.

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, for
heavens sake.

Let's not go overboard looking for things to disagree about ;-)

regards
 Steve
-- 
Steve Holden           +1 571 484 6266   +1 800 494 3119
PyCon 2011 Atlanta March 9-17       http://us.pycon.org/
See Python Video!       http://python.mirocommunity.org/
Holden Web LLC                 http://www.holdenweb.com/