{"action":"created","issue":{"url":"https://api.github.com/repos/dask/dask/issues/3442","repository_url":"https://api.github.com/repos/dask/dask","labels_url":"https://api.github.com/repos/dask/dask/issues/3442/labels{/name}","comments_url":"https://api.github.com/repos/dask/dask/issues/3442/comments","events_url":"https://api.github.com/repos/dask/dask/issues/3442/events","html_url":"https://github.com/dask/dask/issues/3442","id":317578899,"number":3442,"title":"Add scheduler= keyword to compute and persist","user":{"login":"mrocklin","id":306380,"avatar_url":"https://avatars3.githubusercontent.com/u/306380?v=4","gravatar_id":"","url":"https://api.github.com/users/mrocklin","html_url":"https://github.com/mrocklin","followers_url":"https://api.github.com/users/mrocklin/followers","following_url":"https://api.github.com/users/mrocklin/following{/other_user}","gists_url":"https://api.github.com/users/mrocklin/gists{/gist_id}","starred_url":"https://api.github.com/users/mrocklin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrocklin/subscriptions","organizations_url":"https://api.github.com/users/mrocklin/orgs","repos_url":"https://api.github.com/users/mrocklin/repos","events_url":"https://api.github.com/users/mrocklin/events{/privacy}","received_events_url":"https://api.github.com/users/mrocklin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-25T11:01:00Z","updated_at":"2018-05-03T14:08:48Z","closed_at":null,"author_association":"OWNER","body":"As discussed in https://github.com/dask/dask/issues/3226#issuecomment-379937925 we should allow a more intuitive replacement for the current `get=` keyword, perhaps something like `compute(..., scheduler='threads')`\r\n\r\nSome questions:\r\n\r\n1.  What are the appropriate names to use?  threads, processes, synchronous ? \r\n2.  How do we handle distributed?  Perhaps a client registers a name 'distributed' in some global registry of schedulers?\r\n3.  Do we keep the `get=` keyword around to be explicit?  Do we deprecate it?\r\n\r\nI'm happy to do this work, though I suspect that @jcrist or @jakirkham might have strong thoughts and or want to do it directly."},"comment":{"url":"https://api.github.com/repos/dask/dask/issues/comments/386308258","html_url":"https://github.com/dask/dask/issues/3442#issuecomment-386308258","issue_url":"https://api.github.com/repos/dask/dask/issues/3442","id":386308258,"user":{"login":"jakirkham","id":3019665,"avatar_url":"https://avatars1.githubusercontent.com/u/3019665?v=4","gravatar_id":"","url":"https://api.github.com/users/jakirkham","html_url":"https://github.com/jakirkham","followers_url":"https://api.github.com/users/jakirkham/followers","following_url":"https://api.github.com/users/jakirkham/following{/other_user}","gists_url":"https://api.github.com/users/jakirkham/gists{/gist_id}","starred_url":"https://api.github.com/users/jakirkham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakirkham/subscriptions","organizations_url":"https://api.github.com/users/jakirkham/orgs","repos_url":"https://api.github.com/users/jakirkham/repos","events_url":"https://api.github.com/users/jakirkham/events{/privacy}","received_events_url":"https://api.github.com/users/jakirkham/received_events","type":"User","site_admin":false},"created_at":"2018-05-03T14:08:48Z","updated_at":"2018-05-03T14:08:48Z","author_association":"OWNER","body":"Whatever we decide here, we should include that syntax in the [single threaded scheduler debugging page]( http://dask.pydata.org/en/latest/debugging.html#use-the-single-threaded-scheduler ) as we don't currently."}}
{"actor":{"display_login":"jakirkham"}}