-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Move dask.async to dask.local #2318
Conversation
In Python 3.7 `async` will become a keyword and `dask.async` will no longer be a valid module name. We move `dask.async` to `dask.scheduler` and deprecate the old module. The documentation has been updated accordingly.
An alternative name I considered was |
Hrm, Is there any way to warn users? Perhaps keep around async.py and fill it with functions that warn, then call the correct method? |
Also thank you for doing this. |
I did that for the two most likely to be used functions. The rest have changed periodically and I would be surprised if they're in use. |
Grand. Thanks
…On Tue, May 9, 2017 at 5:02 PM, Jim Crist ***@***.***> wrote:
Is there any way to warn users? Perhaps keep around async.py and fill it
with functions that warn, then call the correct method?
I did that for the two most likely to be used functions. The rest have
changed periodically and I would be surprised if they're in use.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2318 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AASszDuXnzWTKD1m8SPcUop33d7850U_ks5r4NRSgaJpZM4NV3Yd>
.
|
Renamed to |
Planning to merge tomorrow if no comment. |
async is a proper keyword in python 3.7, finishes work of dask#2318.
async is a proper keyword in python 3.7, finishes work of #2318.
In Python 3.7
async
will become a keyword anddask.async
will no longer be a valid module name. We movedask.async
todask.scheduler
and deprecate the old module. The documentation has been updated accordingly.Fixes #1834.