Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15929
| Path | csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | Étienne Mollier <emollier@debian.org> |
| Newsgroups | linux.debian.maint.python |
| Subject | Re: newer dask release |
| Date | Sat, 15 Jun 2024 11:00:01 +0200 |
| Message-ID | <IPxqp-34Ys-3@gated-at.bofh.it> (permalink) |
| References | <IPmuZ-2XV4-1@gated-at.bofh.it> <IPrEl-319M-3@gated-at.bofh.it> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Sat Jun 15 08:50:36 2024 |
| Old-Return-Path | <emollier@debian.org> |
| 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 | <debian-python@lists.debian.org> archive/latest/21965 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| 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 <jdg@debian.org>, debian-python@lists.debian.org |
| X-Original-Date | Sat, 15 Jun 2024 10:50:17 +0200 |
| X-Original-Message-ID | <Zm1VyVUHDJj5UGK_@fusion.emlwks999.eu> |
| X-Original-References | <ZmyzN4EByUPjReSh@fusion.emlwks999.eu> <4074f18a7e9cefde7200a90ebdc8315608062491.camel@ghic.org> |
| Xref | csiph.com linux.debian.maint.python:15929 |
Show key headers only | View raw
[Multipart message — attachments visible in raw view] - view raw
Hi Diane, Diane Trout, on 2024-06-14: > On Fri, 2024-06-14 at 23:16 +0200, Étienne Mollier wrote: > > Hi Diane, Hi Julian > > > > 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. > > > Yeah I saw that and decided I was overloaded and stopped doing > anything. > > 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: > > > > * the following change[1] is needed to fix a test failure[2]. > > > > [1]: https://github.com/dask/dask/pull/11177 > > [2]: https://github.com/dask/dask/issues/11176 > > > > * dask.distributed failed its supposedly flaky autopkgtest > > with an error which suggests the two packages might have to > > be uploaded in a lockstep: > > 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. 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. > > That all seems promising to me. > > > > > I did not focus a lot on the sphinxdoc issue described in the > > newly opened #1073183. 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. > > > > 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. > > Diane Thank you for your time putting the additional context! Have a nice day, :) -- .''`. Étienne Mollier <emollier@debian.org> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/3, please excuse my verbosity `-
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
newer dask release Étienne Mollier <emollier@debian.org> - 2024-06-14 23:20 +0200
Re: newer dask release Diane Trout <diane@ghic.org> - 2024-06-15 04:50 +0200
Re: newer dask release Étienne Mollier <emollier@debian.org> - 2024-06-15 11:00 +0200
Re: newer dask release Julian Gilbey <jdg@debian.org> - 2024-06-16 15:00 +0200
Re: newer dask release Étienne Mollier <emollier@debian.org> - 2024-06-16 23:00 +0200
Re: newer dask release Étienne Mollier <emollier@debian.org> - 2024-06-16 23:00 +0200
Re: newer dask release Julian Gilbey <julian@d-and-j.net> - 2024-06-17 09:10 +0200
Re: newer dask release Étienne Mollier <emollier@debian.org> - 2024-06-17 20:10 +0200
Re: newer dask release Étienne Mollier <emollier@debian.org> - 2024-06-16 22:50 +0200
csiph-web