Hackable mercurial based on python 2.7

Angel Ezquerra angel.ezquerra at gmail.com
Tue Jun 19 04:49:12 CDT 2012


On Tue, Jun 19, 2012 at 11:34 AM, Mads Kiilerich <mads at kiilerich.com> wrote:
> 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.

OK, so Eduard meant "ignored" in the "mercurial sense". I thought he
meant that the "hg" in the hackable package ignores the hg-python
folder...

So then my question is, given that the windows mercurial binaries are
being updated to use python 2.7, wouldn't it make sense to update to
python 2.7 the python that is bundled with the hackable mercurial
package (in its hg-python folder) as well?


> 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.

That would be awesome.

Thanks,

Angel


More information about the Mercurial-devel mailing list