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

Option to not return Futures #1

Closed
eriknw opened this issue Jul 16, 2021 · 1 comment
Closed

Option to not return Futures #1

eriknw opened this issue Jul 16, 2021 · 1 comment

Comments

@eriknw
Copy link
Owner

eriknw commented Jul 16, 2021

with afar.run, remotely: creates Futures at the end of the context.

Is there a nice way to specify to run the code on a dask worker, and then copy the results locally? In other words, the result is future.result() instead of future.

Options:

  • use a different function/verb, such as with afar.get, remotely:
  • use a different adverb, such as with afar.run, lovingly:
  • use an argument, such as with afar.run(get=True), remotely:

What's the most clear?

@eriknw
Copy link
Owner Author

eriknw commented Jul 17, 2021

Decided to go with afar.get for now.

@eriknw eriknw closed this as completed Jul 17, 2021
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