Stderr and Pythonw

Manlio Perillo NOmanlio_perilloSPAM at libero.it
Wed Jun 30 06:22:51 EDT 2004


On Wed, 30 Jun 2004 04:22:16 GMT, Dennis Lee Bieber
<wlfraed at ix.netcom.com> wrote:

>On 29 Jun 2004 12:25:58 -0700, vm_usenet at yahoo.com (vm_usenet) declaimed
>the following in comp.lang.python:
>
>> When running python code via pythonw, what exactly happens to stderr?
>
>	You aren't invoking programs by typing "pythonw program.py" in a
>command console window, are you?
>
>	pythonw was intended to be used for programs activated by
>clicking on icons in Windows. As such, these programs are presumed to
>have NO CONSOLE I/O, all I/O must be handled by the program creating a
>window (GUI) or file and writing to that.
>
>	Since there is no console expected, none of the std***
>connections are created.
>

This not really corrected.
Actually 'some' std*** connections are created but are usefulness
(and moreover they have a bug).

If you write more than 4096 an exception is raised...


Regards   Manlio Perillo



More information about the Python-list mailing list