Hi Pierre,
This is a classic case of me forgetting to update the release checklist
once we added wheels...
I've pinged Matt who is able to make the missing wheels for 6.9.1, added
a notice in the release checklist, and we should have a way of not going
through Matt within the next couple of releases.
Sorry about this, thanks for the ping.
Raphaël
On 1/30/25 2:32 PM, PIERRE AUGIER wrote:
Hi,
I saw in https://pypi.org/project/mercurial/6.9.1/#files that there are only
very few wheels (only Linux) uploaded for this version.
One can compare with https://pypi.org/project/mercurial/6.9/#files, for which
there are a lot of wheels.
It's a problem for a project uploading wheels not to do it for a new version
(or to do it only partly) since it breaks installs for users for which the
wheel is missing.
For example currently a Windows/macOS user doing `pipx install mercurial` (same
with `pip` or `uv tool`) is going to trigger a compilation of 6.9.1 (and in
most case, it's going to fail because of lack of build dependencies).
For a project uploading wheels, the good practice for a release is to upload
all the wheels and then only after upload the sdist, so that people that just
want to install the package never need to use the sdist.
Raphaël, have the wheel been produced for 6.9.1 ?
Pierre
--
Pierre Augier - CR CNRS http://www.legi.grenoble-inp.fr
LEGI (UMR 5519) Laboratoire des Ecoulements Geophysiques et Industriels
BP53, 38041 Grenoble Cedex, France tel:+33.4.56.52.86.16
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
