RFC: Alternative for exemaker

Adrian Buehlmann adrian at cadifra.com
Sat Jun 23 18:25:18 CDT 2012

On 2012-06-23 14:23, Mads Kiilerich wrote:
> Andrei Polushin wrote, On 06/23/2012 01:24 PM:
>>   2) It assumes the script name is the same as .exe name, but
>>      without the .exe extension (.py extension is not appended)
> Do everything on windows always do The Right Thing if both a hg.exe and 
> hg.py is present? Is there no such thing as custom extension handlers 
> and custom priorities? I wonder if it would be more stable if X.exe 
> looked for something like X_exe.py .

I've been thinking about this a bit.

Andrei is interested to have the hg.exe look for the plain hg.

Mads and I are interested in using hg.exe for the testsuite, where we
have a problem (to some extent) if there is a hg file, so we rename hg
to hg.py before running the testsuite and expect the hg.py to be called
by the hg.exe.

I think Mads' X_exe.py idea is probably also a good one, although I
don't particularly like the name. But I don't feel strongly about it, so
I could live with hg_exe.py. But I propose we use the name:


That is, for the testsuite we rename the hg file to hgexe.py.

To also accomodate for the use case of Andrei, the hg.exe could first
see if there is a hg file and use that if it's there (in the same dir as
hg.exe). If it isn't there, it should require and use hgexe.py instead
(in the same dir as the hg.exe).

But we can surely implement any other scheme as well. Just tell me what
you need and I'll do it.

More information about the Mercurial-devel mailing list