Re: Debugging "broken pipe" (in telnetlib)

2007-07-04 Thread Samuel
Thanks for your comments, Jean-Paul. -- http://mail.python.org/mailman/listinfo/python-list

Re: Debugging "broken pipe" (in telnetlib)

2007-07-03 Thread Jean-Paul Calderone
On Tue, 03 Jul 2007 08:54:25 -0700, Samuel <[EMAIL PROTECTED]> wrote: >On Jul 3, 3:03 pm, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote: >> EPIPE results when writing to a socket for which writing has been shutdown. >> This most commonly occurs when the socket has closed. You need to handle >> thi

Re: Debugging "broken pipe" (in telnetlib)

2007-07-03 Thread Samuel
On Jul 3, 3:03 pm, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote: > EPIPE results when writing to a socket for which writing has been shutdown. > This most commonly occurs when the socket has closed. You need to handle > this exception, since you can't absolutely prevent the socket from being > cl

Re: Debugging "broken pipe" (in telnetlib)

2007-07-03 Thread Jean-Paul Calderone
On Tue, 03 Jul 2007 05:12:22 -0700, Samuel <[EMAIL PROTECTED]> wrote: >Hi, > >When using telnetlib, the connection sometimes breaks with the >following error: > >"error: (32, 'Broken pipe')" > >where the traceback points to > >self.sock.send(buffer) > >in telnetlib.py. The problem is unreproducible