Progress extension and win32

Steve Borho steve at borho.org
Sun Feb 14 16:00:58 CST 2010


On Sun, Feb 14, 2010 at 3:47 PM, Patrick Mézard <pmezard at gmail.com> wrote:
> Le 14/02/10 22:29, Pascal Quantin a écrit :
>> Hi,
>>
>> Le 14/02/2010 22:22, Patrick Mézard a écrit :
>>> Le 14/02/10 22:06, Pascal Quantin a écrit :
>>>
>>>> Hi,
>>>>
>>>> I just tested crew stable (2b57eed1be0b) to see how progress extension
>>>> behaves on Windows and submit a patch to add it to default Mercurial.ini
>>>> file. But I discovered that no progress ui is displayed at all (whereas
>>>> it is working fine on my Linux box). Is it a known issue ?
>>>> BTW, I'm using Python 2.6.4.
>>>>
>>> Works for me on Windows XP with Python 2.5
>>>
>>> Stupid questions:
>>> - Did you enable it?
>>>
>> Good question. Yes I did :) (added progress = in my [extensions] section)
>>> - The progress bar is only displayed if the operations takes more than
>>> 3s by default (progress.delay), could it be that?
>>>
>> I tested it by doing a clone of crew: progress ui was displayed on Linux
>> but not on Windows. Both run python 2.6.4. Could my issue be related to
>> the packaging of hg as an executable by py2exe (I'm using the Inno Setup
>> installer) ?
>
> I just tried with an installer built with "-b 1" and saw a progress bar both for local clones and remote ones.

You need a recent Mercurial version for it to work.. aka one of the
nightly "unstable" builds from thg-winbuild.

I tested it yesterday and it worked perfectly on Windows.  I was
pleasantly surprised.

--
Steve Borho


More information about the Mercurial-devel mailing list