Unicode Windows API, Was: Concerns about using Python's ctypes library on Windows

Adrian Buehlmann adrian at cadifra.com
Mon Aug 1 05:08:58 CDT 2011


On 2011-08-01 09:45, Adrian Buehlmann wrote:
> On 2011-08-01 03:57, 박경국 wrote:
>>> We are certainly not going to rewrite TortoiseHg to spawn a process per
>>> repo just to support someone's weird setup who wants to use something
>>> like fixutf8 in repo A but not in repo B and open both in the same
>>> TortoiseHg window. If a function is wrapped by an extension, it is wrapped.
>>
>> I can't understand why you are calling my case a weird setup.
> 
> Maybe the weirdness is more in how fixutf8 tries to solve your problem.
> 
> Perhaps you should talk to its creator or those who maintain it currently.
> 
>> Is there any other way for me to avoid it without abandoning using TortoiseHg?
> 
> Currently: Not that I know of, without rewriting TortoiseHg.
> 
> TortoiseHg uses a single process that loads python and extensions. thg
> links with the mercurial sources and if an extension wraps a function of
> the mercurial python modules, that function is wrapped for TortoiseHg
> globally. Assuming that this wrapping is limited to a specific repo
> apparently doesn't work.
> 
> And I've explained that you probably have the same problem with subrepos
> that use fixutf8 too (no need to invoke the "TortoiseHg should be
> rewritten card").

FWIW, Lantiq complained in

https://bitbucket.org/tortoisehg/thg/issue/984/repo-specific-extensions-are-applied-to

as well.


More information about the Mercurial-devel mailing list