Please beat on the tip a bit

[Giuseppe Bilotta]

On Mon, 11 Jul 2005 02:08:12 -0400, Andrew Thompson wrote:

> Andrew Thompson wrote:
>> Giuseppe Bilotta wrote:
>> 
>>> Please don't release a new version until the Windows path mess is
>>> solved. There are two possible solutions: the path juggling I
>>> proposed, or installing all of hg in a single folder, instead of
>>> placing the script(s) in a separate place.
>>>
>>> If the files in mercurial are not inteded for use by other programs,
>>> the latter solution makes a lot of sense.
>> 
>> I'm testing what I believe is the most recent version of Giuseppe's 
>> patch: http://www.selenic.com/pipermail/mercurial/2005-July/001849.html
> 
> OK, ignore everything I just posted.
> 
> I keep getting confused as to how you must call the program to have it 
> come up. I was trying to remove any layering I might have put in by 
> calling hg as python hg blah. But thinking about it, I don't think 
> anyone would actually do that, especially since you would have to 
> actually type it something like: python "c:\program files\mercurial\hg" 
> blah...

The problem arises when you have Mercurial installed somehwere, and
you call that while being in a directory where there is a subdirectory
called mercurial.

Simple testcase, with an unpatched mercurial, a default environment
(e.g. no PYTHONPATH) and a default installation (i.e. with hg going in
Script and the other stuff in site-packages):

mkdir test
cd test
mkdir mercurial
<launch mercurial by any means of your choice>

-- 
Giuseppe "Oblomov" Bilotta

"They that can give up essential liberty to obtain
a little temporary safety deserve neither liberty
nor safety." Benjamin Franklin