[PATCH STABLE] ignore python folder included within hackable hg packages
mads at kiilerich.com
Tue Sep 9 19:02:12 CDT 2014
On 09/09/2014 08:44 PM, Steve Borho wrote:
> # HG changeset patch
> # User Steve Borho <steve at borho.org>
> # Date 1410288246 -7200
> # Tue Sep 09 20:44:06 2014 +0200
> # Branch stable
> # Node ID 9287bf0cdcc890e63f9a596f9e335a9b72a9532c
> # Parent 71227dc24311b6d83904c50bacf7b339b1454bec
> ignore python folder included within hackable hg packages
> the exewrapper.c that builds hg.exe for the hackable hg packages allows two
> names for the Python install folder, hg-python or python2N where N matches the
> minor version of Python you compiled against.
Where / how do the python2N/ stuff happen? Have you tried it? AFAIK it
has a mechanism for loading python2x.dll from $PATH but no direct
alternative to hg-python.
I have a vague recollection that the exewrapper search for hg-python
only works if the hg.exe is invoked with a path (or in same directory) -
it doesn't work to place the hackable directory with hg.exe in $PATH.
Running the tests on windows thus broke and required another hack ...
and that turned out to be to install a global python with the dlls in
$PATH and not use hackable at all, or perhaps just to set $PYTHONHOME.
> the hg-python/ path is only checked when PYTHONHOME is found in the environment,
> for reasons that are just beyond my comprehension. So it is easier for me to
> just use python27/ for my hackable-hg packages but this path is not yet ignored.
> diff -r 71227dc24311 -r 9287bf0cdcc8 .hgignore
> --- a/.hgignore Tue Sep 02 03:41:01 2014 +0200
> +++ b/.hgignore Tue Sep 09 20:44:06 2014 +0200
> @@ -59,5 +59,6 @@
> # hackable windows distribution additions
More information about the Mercurial-devel