Skip to content

Conversation

@martindurant
Copy link
Member

Fixes #172

@martindurant
Copy link
Member Author

This outright errors, which is the extreme of warning. Not sure if you wanted to go that far @CJ-Wright .

@CJ-Wright
Copy link
Member

I guess one could come up with a very wonky use case which runs operations on the Futures objects themselves which would require hooking up dask/not dask streams but that seems like a very janky use case and maybe we shouldn't support unless people demand it.


def __init__(self, upstream=None, upstreams=None, stream_name=None,
loop=None, asynchronous=None, ensure_io_loop=False):
from .dask import DaskStream
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This creates a dependency on Dask?

if (all(isinstance(u, DaskStream) for u in upstreams) !=
any(isinstance(u, DaskStream) for u in upstreams)):
raise ValueError('Must combine only DaskStreams '
'or no DaskStreams')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there no valid use cases of doing this?

@martindurant
Copy link
Member Author

OK, we can close this as overenthusiastic, following comments.

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.

3 participants