[PATCH 0 of 3] hgkeyring extension

Markus Zapke-Gründemann markuszapke at gmx.net
Fri Aug 24 05:06:58 CDT 2012

Pierre-Yves David schrieb:
> On Fri, Aug 24, 2012 at 11:40:16AM +0200, Markus Zapke-Gründemann wrote:
>> This is the port of the mercurial_keyring extension to the core. The new
>> extension is named hgkeyring.
> Which the new name? Aren't Do you break some backward compatibility in the
> configuration or something ?
mercurial_keyring is a Python package[1]. You install it with something like:

pip install mercurial_keyring

Then you activate it like so:

mercurial_keyring =

The rest of the extension's configuration happens in the auth section:

myremote.schemes = http https
myremote.prefix = hg.example.com/repo
myremote.username = alice

So users of mercurial_keyring would just have to uninstall the Python package
and exchange mercurial_keyring with hgkeyring in their extensions section.

IMO it's better to have a different name so users can easily understand which
extension they are using.

If a user would have both, mercurial_keyring and a mercurial version with the
bundled extension it would depend on the import order which extension would be
used. The new name prevents that.



[1] http://pypi.python.org/pypi/mercurial_keyring

More information about the Mercurial-devel mailing list