-
-
Notifications
You must be signed in to change notification settings - Fork 728
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
Rename futures to tasks #8497
base: main
Are you sure you want to change the base?
Rename futures to tasks #8497
Conversation
cff2383
to
d8fbfaa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. I'm excited to see this being taken on. Definitely a big project though!
I pointed out some cases where we're probably being over-zealous in naming. Additionally, I think that we should care about a smooth transition (like naming Future = Task
for backwards compatibility for now) and probably also thinking about adding some redirects in dask docs (this is easy to do in conf.py).
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 27 files ±0 27 suites ±0 10h 7m 19s ⏱️ + 8m 53s For more details on these failures, see this check. Results for commit abab923. ± Comparison against base commit 4425516. This pull request removes 27 and adds 27 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
d8fbfaa
to
abab923
Compare
Closes #8028
Depends on dask/dask#10906
TODO: Before merge, drop commit setting this branch for dask dependency in environment files.
It was a bit of a gray area for where the renaming should stop when considering user interface, then I could easily get confused when we're calling something a Task externally, but Future internally. So, I wrote a script to rename everything. Simple regex-search-replace won't work AFAIK b/c we have plenty of legitimate "future" references w/ asyncio, concurrent.futures etc.
Here's the current iteration of the script: