Py2exe - Bad File Descriptor

T misceverything at gmail.com
Tue Mar 2 01:41:57 CET 2010


On Feb 28, 10:00 pm, Dennis Lee Bieber <wlfr... at ix.netcom.com> wrote:
> On Sun, 28 Feb 2010 13:22:19 -0800 (PST), T <misceveryth... at gmail.com>
> declaimed the following in gmane.comp.python.general:
>
> > Sorry for the lack of code - yes, it does try to write to the
> > console.  From what I'm finding, this error may be due to the fact
> > that there is no "console" to write to when I'm logged off.  However,
> > I would like to be able to print to screen if I run the EXE in debug
> > mode (i.e. "myservice.exe debug").  Do you know of any way around
> > this?  Also, I need to get the output generated from an external EXE -
> > will subprocess.Popen cause problems if I use stdout=PIPE?  Thanks for
> > your help!
>
>         True services typically don't have interactive (console) type I/O...
> What is more likely to work is to have an open socket waiting for
> connections, and the use of a separate user-space client that connects
> to the socket...
> --
>         Wulfraed         Dennis Lee Bieber               KD6MOG
>         wlfr... at ix.netcom.com      HTTP://wlfraed.home.netcom.com/

So how would that work..would the program buffer all the "print"
output, then send it to the client when it connects?  Do you happen to
know of any available code that utilizes this method, or something
similar?  Thanks for your help.



More information about the Python-list mailing list