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

Loading dask.distribute.Client fails with 2022.12.0 #9720

Closed
habi opened this issue Dec 6, 2022 · 4 comments
Closed

Loading dask.distribute.Client fails with 2022.12.0 #9720

habi opened this issue Dec 6, 2022 · 4 comments
Labels

Comments

@habi
Copy link

habi commented Dec 6, 2022

I have a project that uses an environment.yaml file, in which I load dask.
I am (currently) not pinning version numbers.

I've generated the conda environment on a new machine today and do this below in a Jupyter notebook.

import dask
from dask.distributed import Client
print(dask.__version__)
client = Client()

prints "2022.12.0" and fails with "AttributeError: 'Nanny' object has no attribute 'add_done_callback'"

The same code on a machine on which I've installed the environment a while ago prints "2022.05.0" and produces a Client/LocalCluster where I can connect to with dask-labextension.

@github-actions github-actions bot added the needs triage Needs a response from a contributor label Dec 6, 2022
@jrbourbeau
Copy link
Member

Thanks for reporting @habi. What version of Python are you using? FWIW I've seen that error before when using Pyhon 3.11, which Dask doesn't currently support (xref #9691)

@habi
Copy link
Author

habi commented Dec 7, 2022

Indeed, the fresh install on that machine installed Python 3.11.0, too.

Adding python=3.10 to my environment.yaml file and recreating the conda environment works as expected, e.g. I can create a Client/LocalCluster with dask version "2022.12.0".

As I'm not very proficient with working with environment files, it it customary to pin the 'current' versions of the imports?

@phobson
Copy link
Contributor

phobson commented Dec 7, 2022

@habi the specificity with which you're pinning something depends on your use case and personal preference. At any rate, I personally feel that one should always pin python version.

@phobson phobson added upstream and removed needs triage Needs a response from a contributor labels Dec 7, 2022
@jrbourbeau
Copy link
Member

Great, thanks for the feedback @habi -- for now I'd stick with python<3.11. I'm going to close this as a duplicate of #9691. We're currently working on Python 3.11 support and hope to have it released soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants