On Tue, Jul 13, 2010 at 12:19 AM, Titus von der Malsburg <malsburg at 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 | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4