{"action":"created","issue":{"url":"https://api.github.com/repos/ContinuumIO/dask/issues/595","labels_url":"https://api.github.com/repos/ContinuumIO/dask/issues/595/labels{/name}","comments_url":"https://api.github.com/repos/ContinuumIO/dask/issues/595/comments","events_url":"https://api.github.com/repos/ContinuumIO/dask/issues/595/events","html_url":"https://github.com/ContinuumIO/dask/issues/595","id":101562256,"number":595,"title":"investigate using dask in sklearn's grid search and pipelines","user":{"login":"cowlicks","id":598099,"avatar_url":"https://avatars.githubusercontent.com/u/598099?v=3","gravatar_id":"","url":"https://api.github.com/users/cowlicks","html_url":"https://github.com/cowlicks","followers_url":"https://api.github.com/users/cowlicks/followers","following_url":"https://api.github.com/users/cowlicks/following{/other_user}","gists_url":"https://api.github.com/users/cowlicks/gists{/gist_id}","starred_url":"https://api.github.com/users/cowlicks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cowlicks/subscriptions","organizations_url":"https://api.github.com/users/cowlicks/orgs","repos_url":"https://api.github.com/users/cowlicks/repos","events_url":"https://api.github.com/users/cowlicks/events{/privacy}","received_events_url":"https://api.github.com/users/cowlicks/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-08-18T03:27:53Z","updated_at":"2015-08-18T14:33:04Z","closed_at":null,"body":"cc @amueller\r\n\r\nMy understanding  is that sklearn is using joblib in for pararllelizing their pipelines and gridsearches, but there is room for improvement.\r\n\r\nFor example in the pipelines, when the last part of a pipeline is changed, the entire thing is recomputed. But the results from the first part of the pipeline could be reused, but they are not."},"comment":{"url":"https://api.github.com/repos/ContinuumIO/dask/issues/comments/132232458","html_url":"https://github.com/ContinuumIO/dask/issues/595#issuecomment-132232458","issue_url":"https://api.github.com/repos/ContinuumIO/dask/issues/595","id":132232458,"user":{"login":"mrocklin","id":306380,"avatar_url":"https://avatars.githubusercontent.com/u/306380?v=3","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},"created_at":"2015-08-18T14:33:04Z","updated_at":"2015-08-18T14:33:04Z","body":"Dask.imperative and writing dictionaries directly are roughly equivalent in terms of capability.  It's just a question of style.  Internally we tend to stick to dictionaries because this allows us to specify the key names explicitly; this is useful for debugging.  However dictionaries limits the pool of potential co-developers; imperative may be better from a community standpoint."}}