Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!border1.nntp.ams1.giganews.com!nntp.giganews.com!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.030 X-Spam-Evidence: '*H*': 0.94; '*S*': 0.00; 'from:addr:ethan': 0.09; 'from:addr:stoneleaf.us': 0.09; 'from:name:ethan furman': 0.09; 'message-id:@stoneleaf.us': 0.09; 'exception': 0.13; 'failed.': 0.16; 'send.': 0.16; 'subject:send': 0.16; 'wrote:': 0.16; ';-)': 0.18; '>>>': 0.20; 'fine,': 0.22; 'lawrence': 0.22; 'am,': 0.23; 'header:In-Reply-To:1': 0.24; 'header:User-Agent:1': 0.26; 'error': 0.27; 'rest': 0.28; 'went': 0.28; '~ethan~': 0.29; 'print': 0.31; 'especially': 0.32; 'add': 0.34; 'to:addr:python- list': 0.35; 'but': 0.36; 'received:10': 0.37; 'subject:: ': 0.37; 'means': 0.39; 'pm,': 0.39; 'to:addr:python.org': 0.39; 'mark': 0.40; 'why': 0.40; 'talking': 0.67; 'cecil': 0.84; 'received:10.1.10': 0.84; 'westerhof': 0.84; 'ethan': 0.91; 'furman': 0.91 Date: Wed, 03 Jun 2015 16:15:51 -0700 From: Ethan Furman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Retrying to send message References: <87egltht87.fsf@Equus.decebal.nl> <876174ix9n.fsf@Equus.decebal.nl> <556F4766.5090500@stoneleaf.us> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 16 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1433373373 news.xs4all.nl 2903 [2001:888:2000:d::a6]:48575 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:92012 On 06/03/2015 01:37 PM, Mark Lawrence wrote: > On 03/06/2015 19:28, Ethan Furman wrote: >> On 06/03/2015 09:15 AM, Cecil Westerhof wrote: >> >>> I kept the except. I like to see the message that went wrong. ;-) >> >> That's fine, but then add a `raise` after you print the error so you can >> see the reason that message failed. >> > > Why bother in the first place, especially when you're developing? Far easier to let the exception bubble up, or are we talking cross purposes? I think Cecil means he wants to see which twitter message failed to send. The rest of us would like to also have the error itself displayed. ;) -- ~Ethan~