Skip to content
This repository has been archived by the owner on Oct 14, 2018. It is now read-only.

Reassure users of solid parts of this library #9

Closed
mrocklin opened this issue Jan 24, 2017 · 2 comments
Closed

Reassure users of solid parts of this library #9

mrocklin opened this issue Jan 24, 2017 · 2 comments

Comments

@mrocklin
Copy link
Member

It seems that the pipeline and gridsearch components of this library are more stable than the "do not use" disclaimer would lead users to believe. We should find some graceful way of reassuring users that they can uses these components with more confidence than with other parts of the library.

Some options:

  1. Remove "do not use" label entirely. Possibly
  2. Create a dask.learn submodule in the core dask project and only import the solid parts. This is what we do for dask.distributed
  3. ?

cc @jcrist

@jcrist
Copy link
Member

jcrist commented Jan 24, 2017

I'd still not consider this solid/useful enough to be part of dask core. My vote is just to expand the readme to clarify the status a bit better. Good enough?

@mrocklin
Copy link
Member Author

mrocklin commented Jan 24, 2017 via email

jcrist added a commit to jcrist/dask-searchcv that referenced this issue Jan 27, 2017
Describe project status in readme. Fixes dask#9.
@jcrist jcrist mentioned this issue Jan 27, 2017
jcrist added a commit to jcrist/dask-searchcv that referenced this issue Jan 27, 2017
Describe project status in readme. Fixes dask#9.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants