None: break self.write(chunk) fetch_future = convert_yielded(self.fetch_next_chunk()) yield self.flush() This is a little easier to do with decorated coroutines, because they start immediately when called: fetch_future if chunk is None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() Looping In native coroutines, async for can be used. In older versions of Python, looping is tricky and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop

None: break self.write(chunk) fetch_future = convert_yielded(self.fetch_next_chunk()) yield self.flush() This is a little easier to do with decorated coroutines, because they start immediately when called: fetch_future if chunk is None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() Looping In native coroutines, async for can be used. In older versions of Python, looping is tricky and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop

self.write(chunk) fetch_future = convert_yielded(self.fetch_next_chunk()) yield self.flush() This is a little easier to do with decorated coroutines, because they start immediately when called: None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() Looping In native coroutines, async for can be used. In older versions of Python, looping is tricky and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop

None: break self.write(chunk) fetch_future = convert_yielded(self.fetch_next_chunk()) yield self.flush() This is a little easier to do with decorated coroutines, because they start immediately when called: fetch_future if chunk is None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() Looping In native coroutines, async for can be used. In older versions of Python, looping is tricky and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop

Documentation Tornado Documentation, Release 4.5.3 fetch_future = self.fetch_next_chunk() yield self.flush() This pattern is most usable with @gen.coroutine. If fetch_next_chunk() uses async def, then it and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop write(chunk) Writes the given chunk to the output buffer. To write the output to the network, use the flush() method below. If the given chunk is a dictionary, we write it as JSON and set the Content-Type

self.write(chunk) fetch_future = convert_yielded(self.fetch_next_chunk()) yield self.flush() This is a little easier to do with decorated coroutines, because they start immediately when called: None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() Looping In native coroutines, async for can be used. In older versions of Python, looping is tricky and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop

None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() This pattern is most usable with @gen.coroutine. If fetch_next_chunk() uses async def, then it and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop write(chunk) Writes the given chunk to the output buffer. To write the output to the network, use the flush() method below. If the given chunk is a dictionary, we write it as JSON and set the Content-Type

self.write(chunk) fetch_future = convert_yielded(self.fetch_next_chunk()) yield self.flush() This is a little easier to do with decorated coroutines, because they start immediately when called: None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() Looping In native coroutines, async for can be used. In older versions of Python, looping is tricky and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop

None: break self.write(chunk) fetch_future = convert_yielded(self.fetch_next_chunk()) await self.flush() This is a little easier to do with decorated coroutines, because they start immediately when called: fetch_future if chunk is None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() Looping In native coroutines, async for can be used. In older versions of Python, looping is tricky and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop

None: break self.write(chunk) fetch_future = convert_yielded(self.fetch_next_chunk()) await self.flush() This is a little easier to do with decorated coroutines, because they start immediately when called: fetch_future if chunk is None: break self.write(chunk) fetch_future = self.fetch_next_chunk() yield self.flush() Looping In native coroutines, async for can be used. In older versions of Python, looping is tricky and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread. If you use multiple threads it is important to use IOLoop