From pierre.augier at univ-grenoble-alpes.fr  Mon Feb  2 09:56:05 2026
From: pierre.augier at univ-grenoble-alpes.fr (PIERRE AUGIER)
Date: Mon, 2 Feb 2026 10:56:05 +0100 (CET)
Subject: [SPAM] Re: error with 7.2: module 'mercurial.bundle2' has no
 attribute 'parthandler'
In-Reply-To: <ba6992f0-acfd-4757-bf2c-0c128a1cbb9c@ens-lyon.org>
References: <aXzCW1SvyXwKnEi+@t470.reto>
 <ba6992f0-acfd-4757-bf2c-0c128a1cbb9c@ens-lyon.org>
Message-ID: <1620420353.15003575.1770026165175.JavaMail.zimbra@univ-grenoble-alpes.fr>



--
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

----- Mail original -----
> De: "Pierre-Yves David" <pierre-yves.david at ens-lyon.org>
> ?: "mercurial" <mercurial at lists.mercurial-scm.org>
> Envoy?: Vendredi 30 Janvier 2026 15:48:43
> Objet: [SPAM] Re: error with 7.2: module 'mercurial.bundle2' has no attribute 'parthandler'

> On 1/30/26 15:38, Marcos Cruz wrote:
> 
> 
> 
> i have upgraded from 7.1.2 to 7.2 (on debian 13.3, x86_64) the usual
> way:
> 
> ```
> 
> 
> 
> pipx upgrade mercurial --include-injected
> upgraded package mercurial from 7.1.2 to 7.2 (location:
> /home/USER/.local/pipx/venvs/mercurial)
> upgraded package hg-evolve from 11.1.9 to 12.0.0 (location:
> /home/USER/.local/pipx/venvs/mercurial)
> hg-git is already at latest version 1.2.0 (location:
> /home/USER/.local/pipx/venvs/mercurial)
> ```
> 
> now, before executing any command, mercurial prints the following error,
> related to the set up of hggit
> 
> ```
> Traceback (most recent call last):
>  File
>  "/home/USER/.local/pipx/venvs/mercurial/lib/python3.13/site-packages/mercurial/extensions.py",
>  line 291, in _runextsetup
>    extsetup(ui)
>    ~~~~~~~~^^^^
>  File
>  "/home/USER/.local/pipx/venvs/mercurial/lib/python3.13/site-packages/mercurial/exthelper.py",
>  line 227, in finalextsetup
>    c(ui)
>    ~^^^^
>  File
>  "/home/USER/.local/pipx/venvs/mercurial/lib/python3.13/site-packages/hggit/bundle.py",
>  line 76, in install_server_support
>    @bundle2.parthandler(BUNDLEPART_MAP)
>     ^^^^^^^^^^^^^^^^^^^
> AttributeError: module 'mercurial.bundle2' has no attribute 'parthandler'
> *** failed to set up extension hggit: module 'mercurial.bundle2' has no
> attribute 'parthandler'
> ```
> 
> is it an incompatibility between mercurial 7.2 and hggit 1.2.0?
> 
> 
> 
> 
> 
> Yes, the work to make it hggit compatible with 7.2 should ideally have happened
> during the 7.2rc period. However hggit is maintained by volunteer and they
> missed the windows for 7.2.
> 
> The incompatibility have been reported here : [
> https://foss.heptapod.net/mercurial/hg-git/-/issues/456 |
> https://foss.heptapod.net/mercurial/hg-git/-/issues/456 ]
> 
> For use case where you need hg-git, You can downgrade to 7.1 in the meantime.

Warning, the last hg-git version on PyPI is not compatible with Mercurial 7. In practice, for Mercurial 7.1.2, you can use

uv tool install "mercurial<7.2" \
  --with hg-git at https://foss.heptapod.net/mercurial/hg-git/-/archive/branch/default/hg-git-branch-default.tar.gz \
  --with hg-evolve,certifi -p 3.13

> 
> --
> Pierre-Yves David
> 
> _______________________________________________
> Mercurial mailing list
> Mercurial at lists.mercurial-scm.org
> https://lists.mercurial-scm.org/mailman/listinfo/mercurial

From oub at mat.ucm.es  Sun Feb 15 21:39:14 2026
From: oub at mat.ucm.es (Uwe Brauer)
Date: Sun, 15 Feb 2026 22:39:14 +0100
Subject: kwexpand and the default branch
Message-ID: <874inhsn3x.fsf@mat.ucm.es>


Hi for my Latex files I use the following setting
[keyword]
**.tex =
[keywordmaps]
Author = {author|user}
Date = {date|utcdate}
Header = {root}/{file},v {node|short} {date|utcdate} {author|user}
Id = {file|basename},v [{branches}][Num:{rev}] {date|utcdate} {author|user} Exp {author|user}
RCSfile = {file|basename},v
Revision = {node|short}
Source = {root}/{file},v

That works nicely, but only for branches different that are different
from the default branch.

The default branch is not expanded/displayed by 
hg kwexpand

Is this a bug, a missing feature or design decision?

Regards


Uwe Brauer 


-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel.
Stop the war in Gaza, guarantee humanitarian aid, and bring the hostages back.
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5684 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20260215/a5d993d0/attachment.p7s>

From bcc at phloxic.productions  Mon Feb 16 10:02:20 2026
From: bcc at phloxic.productions (Christian Ebert)
Date: Mon, 16 Feb 2026 10:02:20 +0000
Subject: kwexpand and the default branch
In-Reply-To: <874inhsn3x.fsf@mat.ucm.es>
References: <874inhsn3x.fsf@mat.ucm.es>
Message-ID: <aZLrLLEXGTxrzdtr@krille.phloxic.productions>

Hi Uwe,

* Uwe Brauer via Mercurial on Sunday, February 15, 2026 at 22:39:14 +0100:
> Hi for my Latex files I use the following setting
> [keyword]
> **.tex =
> [keywordmaps]
> Author = {author|user}
> Date = {date|utcdate}
> Header = {root}/{file},v {node|short} {date|utcdate} {author|user}
> Id = {file|basename},v [{branches}][Num:{rev}] {date|utcdate} {author|user} Exp {author|user}
> RCSfile = {file|basename},v
> Revision = {node|short}
> Source = {root}/{file},v
> 
> That works nicely, but only for branches different that are different
> from the default branch.
> 
> The default branch is not expanded/displayed by
> hg kwexpand
> 
> Is this a bug, a missing feature or design decision?

Try {branch} instead of {branches}.

`hg help templates` does not list {branches} as keyword.

Not sure why {branches} has an effect at all.

HTH

-- 
LAST SHIP HOME
The circumnavigation of the world of the Peter von Danzig
Winner of the German Ocean Film Award 2019
Watch the movie in full online: https://lastshiphome.de/en/movie

From raphael.gomes at octobus.net  Wed Feb 18 13:44:59 2026
From: raphael.gomes at octobus.net (=?UTF-8?B?UmFwaGHDq2wgR29tw6hz?=)
Date: Wed, 18 Feb 2026 14:44:59 +0100
Subject: Subject: Announcing Mercurial sprint in London, May 27-29th
Message-ID: <1030fd62-f002-44de-a829-4876b6642caf@octobus.net>

We are happy to announce that we will be holding a Mercurial sprint in 
London, UK from May 27th to 29th 2026.

This sprint is intended for a wider audience than the previous Grenoble 
mini-sprint. It aims for Mercurial and Heptapod users, developers and 
other actors in the version control field to gather and discuss their 
needs and help plan for the future.

To deal with diverse topics, the main focus will change over the three days:

Wednesday 27th will lean towards bootstrapping technical contribution 
and discussion of internal matters (tooling, policy, etc.)
Thursday 28th and Friday 29th will gear toward higher-level discussions 
regarding usages, needs, overall direction of the project and 
collaboration opportunities with other tools.

The hosting venue will require attendance details by mid-May, so please 
fill the registration form below in advance.

# General Information

Please refer to the website announcement? for the most up-to-date 
information.

## Location
 ? ? Jane Street Europe
 ? ? 2?, Devonshire Square,
 ? ? London EC2M 4UJ,
 ? ? United Kingdom

## Date
 ? ? May 27th, 28th and 29th

## Opening Hours
 ? ? 09:00 to 18:00
 ? ? (including breakfast, catered lunch and tea time snacks)

## Contact
contact at octobus.net

## Registration form
 ? ? ?https://tally.so/r/XxWgjj

# Detailed Program

You can find the up-to-date list of tentative topics in our tracking issue?.

## Wednesday May 27th

This first day should focus on more technical aspects of Mercurial and 
Heptapod. For example:

- Helping aspiring developers to bootstrap their contributions, and 
occasional contributors to tackle larger issues
- Developer experience, whether that's tooling, processes and other 
technical policies, for example migrating from Black to Ruff
- Technical discussions like internal design choices, deciding how to 
move forward on some bugs and features, bug triage, etc.
- Discussions regarding the project's governance and maintenance
- Tackling some lesser-loved parts of Mercurial and its ecosystem. Last 
year in Grenoble we started and almost finished the wiki and bug tracker 
migration during such an effort
- Other ecosystem related topics like packaging, compatibility 
decisions, etc.

As you probably figured out, if you are interested in the higher-level 
discussions, you can consider skipping that day.

We expect the efforts started on the first day to keep unfolding over 
the next two days, however that first day should take care of most 
general discussions and decision-making on technical aspects. That will 
free up the general attention for the other topics.

## Thursday May 28th and Friday May 29th

During the other two days, we will explore subjects for a more general 
public:

- Presenting the current main development focus for Mercurial, its goals 
and its timelines in order to help users understand what is currently 
going on
- Answering questions about Heptapod, its current state, its strategy 
and its future
- Sharing user stories: What do you do with Mercurial? What are your 
pain points? What requirements would you like to see covered? The goal 
here is to better understand how Mercurial is currently used, the 
emerging use-cases and what the community needs next
- Exchange with developers from other projects: what efforts can we 
share? What are the problems that everybody encounters? What are the 
solutions that Mercurial or its competitors could offer and how do they 
compare? There is a lot of movement in the space nowadays, and this 
renewed energy is a welcome sign that we can create a more diverse and 
stronger community
- Discussions with people unhappy about their current source control 
solution. What makes their tools impractical? Could Mercurial fill the 
gap? What traps should we look out for?

In short, these two days will help core Mercurial and Heptapod 
developers to better understand the needs of the community, provide a 
clearer vision of where Mercurial is headed and ensure the project can 
move forward both faster and in the right direction.

# Sponsoring

Traveling and staying in London can be a significant expense. If these 
costs would prevent you from attending the sprint, check the associated 
box in the form? while registering, as we might be able to sponsor a few 
people.

In order to do so, we need help from companies that are able to 
contribute. If you are willing to help independent contributors to 
attend, get in touch with us at contact at octobus.net.

# Registration

In order to better organize the event, you need to register two weeks in 
advance using the form?. Note that, to make it easier for teams to join 
us, you can register on behalf of multiple people.

Please make sure that you have the required documents to travel to 
London for however long you are planning to stay.

As some of the details might change before the event, we encourage you 
to check the latest information on the Mercurial website?.

See you in London!

[1] https://www.mercurial-scm.org/news/2026/0001-london-sprint
[2] https://tally.so/r/XxWgjj
[3] https://foss.heptapod.net/mercurial/mercurial-devel/-/work_items/10084

From oub at mat.ucm.es  Fri Feb 20 16:55:14 2026
From: oub at mat.ucm.es (Uwe Brauer)
Date: Fri, 20 Feb 2026 17:55:14 +0100
Subject: kwexpand and the default branch
References: <874inhsn3x.fsf@mat.ucm.es>
 <aZLrLLEXGTxrzdtr@krille.phloxic.productions>
Message-ID: <87ms13icct.fsf@mat.ucm.es>



> Hi Uwe,
> * Uwe Brauer via Mercurial on Sunday, February 15, 2026 at 22:39:14 +0100:

> Try {branch} instead of {branches}.

Thanks!


> `hg help templates` does not list {branches} as keyword.

> Not sure why {branches} has an effect at all.


It does at least for me it displays all named branches save the default
branch

While {branch} displays all branches including default.

Not sure why this is so for me.


> HTH



From mischa.becker at kroger.com  Fri Feb 20 21:44:10 2026
From: mischa.becker at kroger.com (Becker, Mischa J)
Date: Fri, 20 Feb 2026 21:44:10 +0000
Subject: kwexpand and the default branch
In-Reply-To: <87ms13icct.fsf@mat.ucm.es>
References: <874inhsn3x.fsf@mat.ucm.es>
 <aZLrLLEXGTxrzdtr@krille.phloxic.productions> <87ms13icct.fsf@mat.ucm.es>
Message-ID: <DM3PPF79DEA11D0D954FE68F49E056628109868A@DM3PPF79DEA11D0.namprd19.prod.outlook.com>

FYI - Template's keyword "branches" only shows up in verbose help because it is depreciated.

    branches      List of strings. The name of the branch on which the
                  changeset was committed. Will be empty if the branch name
                  was default. (DEPRECATED)

Mischa Becker

-----Original Message-----
From: Mercurial <mercurial-bounces at lists.mercurial-scm.org> On Behalf Of Uwe Brauer via Mercurial
Sent: Friday, February 20, 2026 8:55 AM
To: mercurial at mercurial-scm.org
Subject: Re: kwexpand and the default branch

** [EXTERNAL EMAIL]: Do not click links or open attachments unless you recognize the sender and know the content is safe. **

> Hi Uwe,
> * Uwe Brauer via Mercurial on Sunday, February 15, 2026 at 22:39:14 +0100:
> Try {branch} instead of {branches}.

Thanks!

> `hg help templates` does not list {branches} as keyword.
> Not sure why {branches} has an effect at all.

It does at least for me it displays all named branches save the default branch

While {branch} displays all branches including default.

Not sure why this is so for me.

> HTH
_______________________________________________
Mercurial mailing list
Mercurial at lists.mercurial-scm.org<mailto:Mercurial at lists.mercurial-scm.org>
https://urldefense.com/v3/__https://lists.mercurial-scm.org/mailman/listinfo/mercurial__;!!J-PWDud9Isc!k8sK23UhtVrz2IH3oxECtIHjF_J3Vj2d5Kl2R9CGV3p-w3U_vfLEpeOMFDS55RWONwbt_QMOeN74zIbpxINYa8oAiH6i8oXM$



  ________________________________

This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20260220/e0554899/attachment.htm>

From bcc at phloxic.productions  Sat Feb 21 10:11:18 2026
From: bcc at phloxic.productions (Christian Ebert)
Date: Sat, 21 Feb 2026 10:11:18 +0000
Subject: kwexpand and the default branch
In-Reply-To: <DM3PPF79DEA11D0D954FE68F49E056628109868A@DM3PPF79DEA11D0.namprd19.prod.outlook.com>
References: <874inhsn3x.fsf@mat.ucm.es>
 <aZLrLLEXGTxrzdtr@krille.phloxic.productions>
 <87ms13icct.fsf@mat.ucm.es>
 <DM3PPF79DEA11D0D954FE68F49E056628109868A@DM3PPF79DEA11D0.namprd19.prod.outlook.com>
Message-ID: <aZmExosqgicFQh8u@krille.phloxic.productions>

* Becker, Mischa J via Mercurial on Friday, February 20, 2026 at 21:44:10 +0000:
> FYI - Template's keyword "branches" only shows up in verbose help because it is depreciated.
> 
>   branches      List of strings. The name of the branch on which the
>                 changeset was committed. Will be empty if the branch name
>                 was default. (DEPRECATED)

Ah, thanks. That explains it.

-- 
LAST SHIP HOME
The circumnavigation of the world of the Peter von Danzig
Winner of the German Ocean Film Award 2019
Watch the movie in full online: https://lastshiphome.de/en/movie