Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Futures on responses #1

Open
rgbkrk opened this issue Mar 24, 2015 · 1 comment
Open

Futures on responses #1

rgbkrk opened this issue Mar 24, 2015 · 1 comment

Comments

@rgbkrk
Copy link
Member

rgbkrk commented Mar 24, 2015

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:

@rgbkrk
Copy link
Member Author

rgbkrk commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant