]> git.ipfire.org Git - thirdparty/tornado.git/commit
Exceptions in a @return_future function go to both the caller and the Future.
authorBen Darnell <ben@bendarnell.com>
Tue, 19 Feb 2013 04:03:19 +0000 (23:03 -0500)
committerBen Darnell <ben@bendarnell.com>
Tue, 19 Feb 2013 04:03:19 +0000 (23:03 -0500)
commitf695e4e471e503641390a372e5ddf6a67abb3c97
tree2340f66179218e988d6612ead23e5ec676cc3e9b
parent7368cfcca25467709f8afb888846d561759fe072
Exceptions in a @return_future function go to both the caller and the Future.

Add a test for the UnboundLocal error seen here and remove the
no-longer-needed initialization.  I'm not 100% sure we want to do both
(due to the risk of callback-doubling), but the old way where the caller
saw one error and the future resolved to a different error was clearly
incorrect, and leaving the future unresolved doesn't seem right either.
tornado/concurrent.py
tornado/test/concurrent_test.py