Control: tags -1 + confirmed Hi Martin,
Thanks for your report!
Martin Knopp, on 2024-07-03:
> the module version reported by pip list (and contained within
> /usr/lib/python3/dist-packages/distributed/_version.py) is "0+unknown" while
> the package itself is "2024.5.2+ds.1-2". This causes unnecessary
> installations
> when other python code declares a minimum version of distributed (e. g.
> distributed = ">=2022.5.2" in my case).
The faulty version number also leaks through version invocation:
$ python3 -c 'import
distributed;print(distributed._version.get_versions()["version"])'
0+unknown
It is also reflected in a number of other places, like egg file
names, and as you point out, interferes with pip's dependencies
resolver. The minor severity may be slightly underrated.
> I tried to run "python3 setup.py version" on a clone of Salsa's
> "debian/2024.5.2+ds.1-2" tag, that yielded a completely different version
> (2.10.0+ds.1-3.219.g57b69fd) instead of the desired one or "0+unknown", so I
> don't know what's going wrong during build time.
Now to make sense how to reroute the package version number to
the version module, instead of having to rely on a git tag. The
problem during the official package build is that it occurs
completely outside any git context, so no tags have any chance
to be available. It may be possible to capture the package
version instead, but the version.py code to do that is non
existent for now.
The package has still a couple of other issues I'm trying to
diagnose at the moment. With some luck I, or someone else
faster than I am, may come up with something before next upload.
Have a nice day, :)
--
.''`. Étienne Mollier <emoll...@debian.org>
: :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
`. `' sent from /dev/pts/3, please excuse my verbosity
`- on air: Utopianisti - Universe For Dummies
signature.asc
Description: PGP signature
