Hackable mercurial based on python 2.7

[Mads Kiilerich]

On 19/06/12 11:21, Angel Ezquerra wrote:
> On Tue, Jun 19, 2012 at 10:46 AM, Eduard-Cristian Stefan
> <alexandrul.ct at gmail.com> wrote:
>> On Tue, Jun 19, 2012 at 10:36 AM, Angel Ezquerra
>> <angel.ezquerra at gmail.com> wrote:
>>> what do you mean? I don't see a 2.2 hackable mercurial bundle on
>>> http://mercurial.selenic.com/release/windows/hackable/
>> Mercurial 2.2.2 ignores the hg-python folder.
> Sorry if I'm being obtuse, but what do you mean when you say that
> mercurial ignores the hg-python folder. Then why is it there on the
> hackable mercurial package? Is it just in case the user does not have
> python installed?

The hg-python folder is hgignored but will be referenced from the hg.py 
used by hg.exe.

And yes, the whole purpose of 'hackable' is to make it as simple as 
possible to start hacking on Mercurial just by extracting a zip, without 
having python or compilers installed.

A more long term goal is to also include enough of msys to be able to 
run the test suite.

> So you mean that if I place the path to my python 2.7 folder (e.g.
> c:\python27) in my path then the hg-python folder is not needed and
> the hackable mercurial will ignore it and use my system python
> instead?

If you are using an installed Python instead of hg-python then you are 
not using 'hackable'. That is fine too, but should probably be 
documented better.

> If so, what happens if I also have mercurial installed in
> c:\python27\Lib\site-packages?

If you are using 'hackable' then it might be picked up in unexpected 
places unless you set PATH to avoid looking there ... and possibly also 
remove some registry settings and .py handlers.

/Mads