RetroSearch Browse

Wed Jan 9 03:07:42 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-January/123531.html

2013/1/8 Yuriy Taraday <yorik.sar at gmail.com>:
> 4. Why separate exception() from result() for Future class? It does the same
> as result() but with different interface (return instead of raise). Doesn't
> this violate the rule "There should be one obvious way to do it"?

I expect that's a copy-and-paste error. exception() will return the
exception if one occured.

-- 
Regards,
Benjamin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-January/123531.html below:

[Python-Dev] PEP 3156 - Asynchronous IO Support Rebooted