]> git.ipfire.org Git - thirdparty/tornado.git/commit
tornado.concurrent.Future is now always thread-unsafe.
authorBen Darnell <ben@bendarnell.com>
Sun, 26 Jan 2014 03:18:08 +0000 (22:18 -0500)
committerBen Darnell <ben@bendarnell.com>
Sun, 26 Jan 2014 03:18:08 +0000 (22:18 -0500)
commitdce2ffe1b3e20e0592720e5d80709130a11d315e
treedbd63596863e74360163f1c1ace5d370b8f08d7a
parentb1482368b19e75f1ac679ba398af31319f8beb6d
tornado.concurrent.Future is now always thread-unsafe.

This improves performance and provides more consistent semantics
(independent of the presence or absence of the concurrent.futures
package).

The parts of Tornado that accept Futures will accept both Tornado's
thread-unsafe Futures and the thread-safe concurrent.futures.Future.
tornado/concurrent.py
tornado/gen.py
tornado/ioloop.py
tornado/test/concurrent_test.py