This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients brian.curtin, loewis, pitrou, tim.golden
Date 2010-08-15.18:53:42
SpamBayes Score 1.7044782e-05
Marked as misclassified No
Message-id <4C6837B4.10309@v.loewis.de>
In-reply-to <1281897853.3194.7.camel@localhost.localdomain>
Content
> Well, the loop stops when an error status is returned by the raw IO
> layer. At that point, the buffered IO layer re-raises the error after a
> bit of internal cleanup.

Assume the following case:
1. writing starts, and writes some data
2. Ctrl-C is pressed, raises a signal, and interrupts the current
   system call (EINTR)
3. having already written data, the signal is discarded, and the
   number of successfully written bytes is returned.
4. the loop retries to write the rest. Not receiving any signal
   anymore, the subsequent write operations wait for completion.

End consequence: the signal is discarded without any effect.
History
Date User Action Args
2010-08-15 18:53:45loewissetrecipients: + loewis, pitrou, tim.golden, brian.curtin
2010-08-15 18:53:44loewislinkissue9611 messages
2010-08-15 18:53:43loewiscreate