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

Allow duck typing for is_future check #1

Merged
merged 1 commit into from
May 28, 2016

Conversation

Globegitter
Copy link
Contributor

We are using a Future that is not neither a ConcurrentFuture or an AsyncIOFuture, but a GRPC future (https://github.com/grpc/grpc/blob/d0fbba52d6e379b76a69016bc264b96a2318315f/src/python/grpcio/grpc/framework/foundation/future.py#L63). This allows for any Future that implements add_done_callback to be used and resolves our issue.

We are using a Future that is not neither a `ConcurrentFuture` or an `AsyncIOFuture`, but a GRPC future (https://github.com/grpc/grpc/blob/d0fbba52d6e379b76a69016bc264b96a2318315f/src/python/grpcio/grpc/framework/foundation/future.py#L63). This allows for any Future that implements `add_done_callback` to be used and resolves our issue.
@coveralls
Copy link

coveralls commented May 24, 2016

Coverage Status

Coverage increased (+0.6%) to 94.805% when pulling 04690be on Globegitter:patch-1 into 127a202 on syrusakbary:master.

@Globegitter Globegitter changed the title Enable duck_typing for is_future check Allow duck typing for is_future check May 24, 2016
@syrusakbary syrusakbary merged commit 34a033e into syrusakbary:master May 28, 2016
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

Successfully merging this pull request may close these issues.

None yet

3 participants