Skip to content

Futures on responses #1

@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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions