On Fri, 2023-08-04 at 14:02 +0100, Julian Gilbey wrote:
Hi Diane,
I just got emails telling me that some of my packages would be
removed
from testing because they (recursively) (build-)depend on
dask.distributed: https://bugs.debian.org/1042135
Are you able to take a look at this soon, or would you like someone
to
do a team upload?
There is also a newer version available: 2023.7.1, which may well
resolve this.
Last time I tried updating pyarrow wasn't properly optional and we
don't have it packaged. (And it's actually in a single repository that
builds multiple language modules)
Dask has updated their build system some, and let me see if it'll
update.
If I don't manage to get to it, make sure that if you try you have to
update both dask and dask.distributed together, and it's best to makes
sure that you run the dask.distributed tests using the updated dask.
That's where why it's usually been difficult to update.
Thanks so much! I see you've already started on dask :)
I took at quick look at arrow - yikes! There is potentially work
afoot on this though: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970021
Thanks so much! I see you've already started on dask :)
I took at quick look at arrow - yikes! There is potentially work
afoot on this though: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970021
Dask & dask.distributed 2023.8.0 was easier to update than some of the
other versions they had between 2022.12 and now.
Dask would still benifit from pyarrow, by I added enough
pytest.importorskip to avoid triggering the tests that depend on
pyarrow.
It also looks like it builds for me and the debian builder so I closed 1042135.
Hopefully that helps. (And it looks like it's got some code for pandas
2.0 so hopefully that'll help Rebecca Palmer.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 350 |
Nodes: | 16 (2 / 14) |
Uptime: | 09:36:04 |
Calls: | 7,625 |
Files: | 12,793 |
Messages: | 5,686,482 |