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
Consistent use of ordering by task name #3271
Conversation
It also looks like we need to drop the initial call to |
20d678f
to
925e3d3
Compare
Merging this soon if there are no comments |
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.
LGTM
dask/tests/test_order.py
Outdated
@@ -238,8 +240,11 @@ def test_gh_3055(): | |||
|
|||
dsk = dict(w.__dask_graph__()) | |||
o = order(dsk) | |||
# from dask import visualize | |||
# visualize(dsk, color='order', filename='dask.pdf', node_attr={'penwidth': '6'}) |
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.
Commented out code
We break ties in task ordering by using the task key itself. Previously we did this inconsistently due to using
sorted(reverse=True/False)
in different situations. This cause inconsistent ordrering in general and pathological ordering in some situations (like nearest neighbor computations).We now use two different comparators for string comparison.
flake8 dask
docs/source/changelog.rst
for all changesand one of the
docs/source/*-api.rst
files for new API