[Python-Dev] PEP 3156 - Asynchronous IO Support Rebooted (original) (raw)
Guido van Rossum guido at python.org
Wed Jan 9 03:49:50 CET 2013
- Previous message: [Python-Dev] PEP 3156 - Asynchronous IO Support Rebooted
- Next message: [Python-Dev] PEP 3156 - Asynchronous IO Support Rebooted
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Jan 8, 2013 at 6:07 PM, Benjamin Peterson <benjamin at python.org> wrote:
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.
I don't see the typo. It is as Nick explained.
-- --Guido van Rossum (python.org/~guido)
- Previous message: [Python-Dev] PEP 3156 - Asynchronous IO Support Rebooted
- Next message: [Python-Dev] PEP 3156 - Asynchronous IO Support Rebooted
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]