Repository navigation
Futures on responses #1
Description
We've done a bit of musing on how we would use concurrent.futures within a Python 3 version of multyvac/cloud.
This would mean that our underlying network client would need to use either:
We've done a bit of musing on how we would use concurrent.futures within a Python 3 version of multyvac/cloud.
This would mean that our underlying network client would need to use either:
Activity
rgbkrk commentedon Mar 24, 2015
Apparently requests futures uses a ThreadPoolExecutor underneath, which seems like an odd bit to expose controls for. IMO, tornado gets a lot more active development relying on libcurl. We don't get the nicety of the requests interface though.
The sad part about picking async is that our barrier to entry for contributors is a bit higher.