Re: Any ideas Re: #1030096 dask.distributed intermittent autopkgtest fail ?
On Mon, 2023-02-06 at 11:13 +0100, Andreas Tille wrote:
> Hi Rebecca,
>
> Am Mon, Feb 06, 2023 at 07:59:17AM +0000 schrieb Rebecca N. Palmer:
> > (Background: the pandas + dask transition broke dask.distributed
> > and it was
> > hence removed from testing; I didn't notice at the time that if we
> > don't get
> > it back in we lose Spyder.)
>
> as far as I know Diane has put quite some effort into dask and I
> understood that dask and dask.distributed are closely interconnected.
>
Hi now.
My fragments of time were spent fighting with numba, and I didn't have
the energy to be thinking about dask.distributed.
Numba should be in a better place right now. So I can set my build
machine to trying to build it and seeing where we are with it right
now.
The most important thing about dask / dask.distributed is they really
should be at about the same upstream version. I'm not 100% sure how to
mark that in the d/control file. Also upstream might have some ability
to do minor releases independently.
But if we do a new upstream release of dask, it needs to be paired with
a new upstream release of dask.distributed. And in my experience
dask.distributed is the one that's harder to get to work right.
Diane
Reply to: