> Background tasks, spawned off in a ThreadPoolExecutor. This could be very nice; something that I've often found clunky when building a prototype is the amoun

> Background tasks, spawned off in a ThreadPoolExecutor. This could be very nice; something that I've often found clunky when building a prototype is the amount of infrastructure required to get a more full-featured task queue up and running (say Celery or RQ). You can always just run an event loop, but then you have to reinvent a lot of the nice delay/scheduling machinery.