Groups > linux.debian.maint.python > #15930

Re: newer dask release

Path	csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod
From	Julian Gilbey <jdg@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: newer dask release
Date	Sun, 16 Jun 2024 15:00:01 +0200
Message-ID	<IPXEd-3lgJ-21@gated-at.bofh.it> (permalink)
References	<IPmuZ-2XV4-1@gated-at.bofh.it> <IPrEl-319M-3@gated-at.bofh.it> <IPxqp-34Ys-3@gated-at.bofh.it>
X-Original-To	Étienne Mollier <emollier@debian.org>
X-Mailbox-Line	From debian-python-request@lists.debian.org Sun Jun 16 12:59:01 2024
Old-Return-Path	<julian@d-and-j.net>
X-Amavis-Spam-Status	No, score=-109.271 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-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	text/plain; charset=iso-8859-1
Content-Disposition	inline
Content-Transfer-Encoding	8bit
X-Debian-User	jdg
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/21966
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/Zm7hXqs3n8FvKtOP@d-and-j.net
Approved	robomod@news.nic.it
Lines	29
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Cc	Diane Trout <diane@ghic.org>, debian-python@lists.debian.org
X-Original-Date	Sun, 16 Jun 2024 13:58:06 +0100
X-Original-Message-ID	<Zm7hXqs3n8FvKtOP@d-and-j.net>
X-Original-References	<ZmyzN4EByUPjReSh@fusion.emlwks999.eu> <4074f18a7e9cefde7200a90ebdc8315608062491.camel@ghic.org> <Zm1VyVUHDJj5UGK_@fusion.emlwks999.eu>
Xref	csiph.com linux.debian.maint.python:15930

Show key headers only | View raw

On Sat, Jun 15, 2024 at 10:50:17AM +0200, Étienne Mollier wrote:
> > 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.

You could do something like this in the dask.distributed source
package:

Source: dask.distributed
Build-Depends: python3-dask (>> 2024.5.2), python3-dask (<< 2024.5.3~)

and in the binary python3-dask.distributed package similarly:

Depends: python3-dask (>> 2024.5.2), python3-dask (<< 2024.5.3~)

This forces the dask version to match the dask.distributed version.  I
don't know how tight the version numbers need to be, but this works to
keep the packages in step with each other, and will prevent an updated
dask package from migrating if the dask.distributed package has not
been updated in parallel.  Probably more effective than adding
something to README.source (though that will certainly help a bit).

Best wishes,

   Julian

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