Skip to content

Daskversionfix 1v2#3433

Closed
pp-mo wants to merge 2 commits into
SciTools:masterfrom
pp-mo:daskversionfix_1v2
Closed

Daskversionfix 1v2#3433
pp-mo wants to merge 2 commits into
SciTools:masterfrom
pp-mo:daskversionfix_1v2

Conversation

@pp-mo

@pp-mo pp-mo commented Oct 1, 2019

Copy link
Copy Markdown
Member

WIP do not merge

@lbdreyer

lbdreyer commented Oct 1, 2019

Copy link
Copy Markdown
Member

It works ... So I wonder why #3431 doesn't pick up dask 1.2 ? 😕

@pp-mo

pp-mo commented Oct 1, 2019

Copy link
Copy Markdown
Member Author

I wonder why #3431 doesn't pick up dask 1.2 ?

😕 indeed.
N.B. the commit is exactly the same as the first one here.

However, it does seem to be an adequate fix ...

@pp-mo

pp-mo commented Oct 1, 2019

Copy link
Copy Markdown
Member Author

why #3431 doesn't pick up dask 1.2 ?

Comparing the conda list output, the only differences are ...

package "OLD" pin dask>=1.1 // "NEW" pin dask>=1.2
dask (AND dask-core) 1.1.4 py27_1 defaults // 1.2.2 py_3 conda-forge
pyproj 1.9.6 py27h14380d9_0 defaults // 1.9.6 py27h516909a_1002 conda-forge

In fact that's so odd I don't believe it.
Maybe the underlying channels have just shifted ??
I will re-spin the original checks ...

@pp-mo

pp-mo commented Oct 1, 2019

Copy link
Copy Markdown
Member Author

I will re-spin the original checks ...

Nope, still does the same.
:sigh:

@pp-mo pp-mo closed this Oct 2, 2019
@pp-mo pp-mo deleted the daskversionfix_1v2 branch October 17, 2019 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants