Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #97315 > unrolled thread
| Started by | Cameron Simpson <cs@zip.com.au> |
|---|---|
| First post | 2015-10-02 08:52 +1000 |
| Last post | 2015-10-02 08:52 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: ConnectionError handling problem Cameron Simpson <cs@zip.com.au> - 2015-10-02 08:52 +1000
| From | Cameron Simpson <cs@zip.com.au> |
|---|---|
| Date | 2015-10-02 08:52 +1000 |
| Subject | Re: ConnectionError handling problem |
| Message-ID | <mailman.319.1443739969.28679.python-list@python.org> |
On 30Sep2015 23:56, Laura Creighton <lac@openend.se> wrote: >In a message of Thu, 01 Oct 2015 07:30:59 +1000, Cameron Simpson writes: >>Most likely the Ctrl-C interrupts whatever system call is hanging, causing it >>to return (failed, probably with errno EINTR). And the python program resumes >>because the OS system call has returned. > >Shiva Upreti needs to post the current code, but last time I read it >the problem was that control-C is a KeyboardInterrupt, which the >program was catching, and then continuing the loop. Indeed. Cheers, Cameron Simpson <cs@zip.com.au> C makes it easy for you to shoot yourself in the foot. C++ makes that harder, but when you do, it blows away your whole leg. - Bjarne Stroustrup
Back to top | Article view | comp.lang.python
csiph-web