search

dask / dask-expr

BSD 3-Clause "New" or "Revised" License
79 stars 18 forks source link

Time to move to dask/dask? #1086

Open fjetter opened 2 weeks ago

fjetter commented 2 weeks ago

We kept this repo separate because we anticipated a lot of breakage and wanted to have a lean release cycle. I noticed that we're now pinning hard to dask. I believe the time has come where we should merge this to the main repo

cc @phofl @hendrikmakait

phofl commented 2 weeks ago

Any idea when we want to rip out the legacy implementation? That would probably simplify the move over to dask/dask

On Wed, Jun 19, 2024 at 7:24 PM Florian Jetter @.***> wrote:

We kept this repo separate because we anticipated a lot of breakage and wanted to have a lean release cycle. I noticed that we're now pinning hard to dask. I believe the time has come where we should merge this to the main repo

cc @phofl https://github.com/phofl @hendrikmakait https://github.com/hendrikmakait

— Reply to this email directly, view it on GitHub https://github.com/dask/dask-expr/issues/1086, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOYQZGFBANH36WXWACUBLDTZIG5GRAVCNFSM6AAAAABJSONDBWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3DEOBVGMYTAMI . You are receiving this because you were mentioned.Message ID: @.***>