Patrick Hoefler
Patrick Hoefler
I'd be fine with removing the paused_or_retiring metric, my main concern was backward compatibility. We mostly care about paused as @fjetter said
Will this restart the worker immediately or when the thing that is running releases the Gil again/finishes? What I want to know: If my program holds the Gil and thus...
> Things I have done in this PR, other than upgrading to Python 3.12. > > * I have updated the test CI to align more with our other repos....
thx @Hoxbro The issue at play here is as follows: ``` df.__dask_graph__() df.__dask_keys__() ``` both change the expression (a optimization step), which makes the keys in the graph no longer...
That's not as trivial as this one. There are 2 options: - The ideal solution would be to make your ``DaskGeoDataFrame`` compatible with the expression logic. geo pandas did this...
this was fixed on Friday fortunately
> I'm with Joris pretty much across the board on this. I'm pretty sure @phofl will be too. Agreed with @jbrockmendel This would be an acceptable compromise of not requiring...
1 is not really an option, since we can not correctly guess all cases where the behavior would change (I think) I'd be in favour of a DeprecationWarning, removing is...
Quick question: Can you split this somehow (hard to review) or is this all interconnected?
You can ignore the failure, this happens sometimes