On Tue, Jul 13, 2010 at 12:19 AM, Titus von der Malsburg <malsb...@gmail.com> wrote: > This reminds me a lot of how things are done in C but it's not very > pythonic. Wouldn't it be possible and nicer to raise the exception -- > if there was one inside the asynchronous job -- when the result of the > future is accessed?
That's what actually happens, so you can code it either way (either just calling result() and dealing with any exception that was raised, or else checking for a non-None exception value directly). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
