Il 26/08/26 11:47, Alastair McKinstry ha scritto:
On 24/08/2026 07:46, Pieter Lenaerts wrote:
Antonio Valentino <[email protected]> schreef op 24
augustus 2026 08:08:51 CEST:
Dear Diane, all, both dask and python-xarray have been removed
from testing on July the 30th causing the removal of a relatively
large stack of packages that rely on them. Both dask and, most of
all, python-xarray are an important part of the modern Python
scientific stack, so, IMHO, it is a real pity to have them out of
testing for so long time. Apparently there is a quite complex
(circular?) set of dependency involving at least dask,
dask.distributed, python-sparse, python-xarray, python-pint, cfgrib.
If it helps, cfgrib only needs python-xarray for testing; a build with
<!nocheck> currently still depends on python3-xarray, this could be
fixed if it needs to in order to break a circular dependency.
Regards
Alastair
Hi Alastair,
in the python-xarray tracker [1] I see:
Blocked by: python-pint
Migrates after: cfgrib, dask
but cfgrib is
Blocked by: python-xarray
Maybe removing the dependency of cfgrib and python-pint (I could take in
charge of it) could help the migration of python-xarray, but the real
issue, IMHO, is the dependency of python-xarray from dask.
[1] https://tracker.debian.org/pkg/python-xarray
kind regards
--
Antonio Valentino
