Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: =?utf-8?Q?=C3=89tienne?= Mollier Newsgroups: linux.debian.maint.python Subject: Re: newer dask release Date: Sat, 15 Jun 2024 11:00:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Jun 15 08:50:36 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-114.52 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="aIAqwAkwXboDDHHM" Content-Disposition: inline X-Debian-User: emollier X-Mailing-List: archive/latest/21965 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/Zm1VyVUHDJj5UGK_@fusion.emlwks999.eu Approved: robomod@news.nic.it Lines: 109 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Julian Gilbey , debian-python@lists.debian.org X-Original-Date: Sat, 15 Jun 2024 10:50:17 +0200 X-Original-Message-ID: X-Original-References: <4074f18a7e9cefde7200a90ebdc8315608062491.camel@ghic.org> Xref: csiph.com linux.debian.maint.python:15929 --aIAqwAkwXboDDHHM Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Diane, Diane Trout, on 2024-06-14: > On Fri, 2024-06-14 at 23:16 +0200, =C3=89tienne Mollier wrote: > > Hi Diane, Hi Julian > >=20 > > I'm wrapping up that email as it seems to me there could be some > > activity on the dask package from several people at once. >=20 >=20 > Yeah I saw that and decided I was overloaded and stopped doing > anything. >=20 > Historically it was pretty important to dask and dask.distributed to be > released together, upstream intends them to be matching versions, but I > didn't know how to set the the dependnecy version strings to require > that. It makes sense. The construction pretty much looks like the latter is supposed to be a Python submodule of the former. > > I happen to have a look at the dask.dataframe import issues, > > which manifest as at least #1068422, #1069821, and #1069359. > > The import problem looks fixed in 2024.5.2, but the new version > > also introduced a couple of issues: > >=20 > > =C2=A0 * the following change[1] is needed to fix a test failure[2]. > >=20 > > =C2=A0=C2=A0=C2=A0 [1]: https://github.com/dask/dask/pull/11177 > > =C2=A0=C2=A0=C2=A0 [2]: https://github.com/dask/dask/issues/11176 > >=20 > > =C2=A0 * dask.distributed failed its supposedly flaky autopkgtest > > =C2=A0=C2=A0=C2=A0 with an error which suggests the two packages might = have to > > =C2=A0=C2=A0=C2=A0 be uploaded in a lockstep: >=20 > Yes very much yes. Is there a way to nag anyone trying to upload dask > to go check the harder to update distributed before uploading? A mention about the interdependency in d/README.source may help, but getting dask.distributed autopkgtest to not be flaky anymore would prevent migration of a mismatched distribution to testing, and raise some alarms in the maneuver; that is, assuming version mismatch is going to cause test failures in dask.distributed in every cases. > > If that helps, I have the package upgrade staging on my drive, > > and may push to salsa after a good night of sleep.=C2=A0 In case you > > see reasons I missed for not bumping version too soon, or if you > > already went through the upgrade steps already, don't hesitate > > to tell me to hold my horses. >=20 > That all seems promising to me. >=20 > >=20 > > I did not focus a lot on the sphinxdoc issue described in the > > newly opened #1073183.=C2=A0 I'm not very good with dealing with > > sphinxdoc, and would be more tempted to copy the bare rst files > > than getting the html files back on tracks. > >=20 >=20 > If you want to push what you've done I might have time sunday night/ > monday to look at the sphinx problem. Okay, I pushed my work in progress on Salsa, so anyone can build on top of it. In the meantime I can change target and see to move dask.distributed forward. > Dask is probably complicated enough to be a good candidate for team > maintenance. >=20 > Diane Thank you for your time putting the additional context! Have a nice day, :) --=20 .''`. =C3=89tienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/3, please excuse my verbosity `- --aIAqwAkwXboDDHHM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmZtVckACgkQeTz2fo8N Edop1w/+KovJSNvmj4IYBD1Ap7W7k7LYzJTsbgiI7DVeXRXdK9L6C/T27+s3lrXV y5VEkj8NttkLpje8riHO9c7b+pdeFwYb6kFbgVjaXdieruZ4pKtUDwftkINfocww UzUbAbhMmCeubpzO3Ub+SyEh3WIMtW7VBQssW81g9ApxDE9KEQ89Z1HCG05SRxEW MdANN/jFEEh1y8i7gRW84myqwScVQ57HqhJ4XqJuQbagDodBS7xfdsx6QRXQMvEM bosXyVFNKfuk16GVizZ988HS67X2g2UGpHVmOR4fdolOpV1ho0x9YFQ3xbSv2gJY dx48bu/6cEOUSXwwyXuDNenY4SfEr9gRgrkeMzAJsWdqaCuXNyZpVv9YIH0W9OKi 9K38aIROROKqlwYyHyW0bMJXqJGkpn5eNRvCYSljN0y4FtfdMamfs3qK7VgF7xKk SQ5vx2mTlf98rME+dOjZqa8yFTMzIWz8D4edk/rfaTWzikFlxsL6QkjeQH5imGgU aJd7fEZ8iR5i1EeKd8elJ/pg2at/mqrgiHoKte6yH/WyX6nZ7Pf7P2+1OP8Rgex6 xuAddLVLk0JhPQSuMbMBklQC8S5WX/21vCMOWzDNgOpMn6xwq6O4ydgc9tJFsSWa XCxkjD8SaO+5E1Uetpo+gnI+g9K4+g3n/TlV+rzCJrMuCa+Sfng= =YyQW -----END PGP SIGNATURE----- --aIAqwAkwXboDDHHM--