Closed mrocklin closed 7 years ago
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?
Sure
On Tue, Jan 24, 2017 at 3:11 PM, Jim Crist notifications@github.com wrote:
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?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dask/dask-learn/issues/9#issuecomment-274924349, or mute the thread https://github.com/notifications/unsubscribe-auth/AASszFEo_J-_nl7JE8fcSYBx0rH-Uig2ks5rVlsKgaJpZM4LsuUh .
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:
dask.learn
submodule in the core dask project and only import the solid parts. This is what we do fordask.distributed
cc @jcrist