[PATCH] test-commandserver: use python instead of hg as the executable

[Matt Mackall]

On Sun, 2012-06-17 at 11:23 +0200, Adrian Buehlmann wrote:
> # HG changeset patch
> # User Adrian Buehlmann <adrian at cadifra.com>
> # Date 1339924726 -7200
> # Node ID 20c4d99cc7e96666de519418df51b6d5b7d9fad2
> # Parent  a0f221f45f846aea982355840c614d6fced41edb
> test-commandserver: use python instead of hg as the executable

I'm not thrilled about this approach. We certainly expect "hg" to be
executable, and it's simply a deferred bug of our Windows build process
that it doesn't result in something called "hg" you can run.

(And it's only deferred because the traditional methods of making a
Python script executable on Windows all have rather large caveats.)

But I don't think it's a quirk we want to enshrine in the test suite.
It'd be better if we put a single gross hack in run-tests so that it
just works. For instance, if no suitable hg is present, building an
hg.cmd and sticking it in $TMP somewhere, then adding it to the path.

ps: Wanted: benchmark comparison of startup times for .cmd, exemaker,
and py2exe variants.

-- 
Mathematics is the supreme nostalgia of our time.