Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #5904 > unrolled thread

Re: Overuse of try/except/else?

Started byJames Mills <prologic@shortcircuit.net.au>
First post2011-05-21 17:08 +1000
Last post2011-05-21 17:08 +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.


Contents

  Re: Overuse of try/except/else? James Mills <prologic@shortcircuit.net.au> - 2011-05-21 17:08 +1000

#5904 — Re: Overuse of try/except/else?

FromJames Mills <prologic@shortcircuit.net.au>
Date2011-05-21 17:08 +1000
SubjectRe: Overuse of try/except/else?
Message-ID<mailman.1875.1305961727.9059.python-list@python.org>
On Sat, May 21, 2011 at 3:40 PM, Cameron Simpson <cs@zip.com.au> wrote:
> These days I think I'd use a LateFunction (a facility of my own which is
> a lot like the futures module) which returns a callable when you submit
> a function; the worker thread runs the submitted function and catches the
> return value or raised exception. Anyone who calls the returned callable
> later gets the return value or the exception reraised as appropriate,
> so one can avoid the dangerous "catch everything and log" scenario.

I like this :) I guess you call this a Proxy Object although
your calling it a LateFunction seems more "fitting" :)

cheers
James

-- 
-- James Mills
--
-- "Problems are solved by method"

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web