Phillip Cloud

> rewrite the dask backend to use dask-expr instead of removing it entirely This is purely additional work, without any benefit. Concretely, who is using the dask backend and would...

@gforsyth @jcrist @lostmygithubaccount @kszucs @ncclementi I would really like to avoid this PR stalling. I think we should include this as a breaking change for 10.0.

Is there any reason to wait? Here are the scenarios: ## plan to remove in 10.0 1. someone complains after we remove it and we revert (requires a bump to...

After talking with @ianmcook I think we should give a small buffer for folks to move away from Dask/Pandas. Next steps are: 1. Write a blog stating we're removing both...

Started going through and cleaning up deprecations. I'm going to submit a separate PR for each removal. In the first PR I'll disable the deprecation check in the release verification...

ok I'm going to back out all the changes and just keep the backend removal i will disable the check for deprecation in the release dry run script for now,...

Thanks for the issue! Can you show an example of how you might like to use such an API? We can iterate on the design a tiny bit and see...

Thanks for the issue! Not sure if I'd categorize this as a bug. We don't test against Fabric and the various MS SQLs seem to be wildly incompatible with each...

This requires some support on the Fabric side. Would be great to get a conversation going. @djouallah friendly ping!

@tokoko Thanks for opening this issue. It has been nice as a developer of to not have to deal with a large range of Python versions, but as adoption keeps...