Skip to content

Futures on responses #1

Open
Open
@rgbkrk

Description

@rgbkrk

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

rgbkrk commented on Mar 24, 2015

@rgbkrk
MemberAuthor

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Futures on responses · Issue #1 · cloudpipe/sdk-python3