Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.glorb.com!news-out.readnews.com!transit4.readnews.com!panix!gordon From: John Gordon Newsgroups: comp.lang.python Subject: Re: improving performance of writing into a pipe Date: Wed, 20 Feb 2013 18:39:05 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 18 Message-ID: References: <76620a9e-45fe-499d-b1bf-06b1d2a91c25@googlegroups.com> <16e85bd1-6e5d-4d70-95bf-cc6b986a9f7c@googlegroups.com> <8f26ac4d-4732-46ac-bf4e-877696b22241@googlegroups.com> <85cd2254-0800-4448-9117-9175bbfd10f6@googlegroups.com> NNTP-Posting-Host: panix3.panix.com X-Trace: reader1.panix.com 1361385545 7441 166.84.1.3 (20 Feb 2013 18:39:05 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Wed, 20 Feb 2013 18:39:05 +0000 (UTC) User-Agent: nn/6.7.3 Xref: csiph.com comp.lang.python:39372 In mikprog@gmail.com writes: > As written before, I don't know what exception to search for, so I wrote > the (wrong) code: > except: > print "error" > Let's why I don't have a clue about it. > But someone already explained me that I should not do this. If you don't know what exception is being raised, temporarily remove the try/except statements and run the code directly. You'll get the exception, and then you'll know which one it is. -- John Gordon A is for Amy, who fell down the stairs gordon@panix.com B is for Basil, assaulted by bears -- Edward Gorey, "The Gashlycrumb Tinies"