Strange mercurial behaviour

[Mathieu Clabaut]

ok,
but the invoked script comes from /usr/bin (neither interactive interpreter
nor stdin).
And the result is I'm unable to update a mercurial repository which contains
a faulty mercurial version.... I find this quite annoying.
(and, non I have no solution to propose... Sorry, I did not take time to
investigate...:( )

Anyway, thank you for the manual reference Christian ;)


-mathieu

On 2/7/07, Christian Ebert <blacktrash at gmx.net> wrote:
>
> * Mathieu Clabaut on Wednesday, February 07, 2007 at 09:17:51 +0100:
> > What is strange is that mercurial use the modules in the current working
> > directory and not in the system wide directory.
>
> Read the fine manual ;)
>
> As initialized upon program startup, the first item of this list,
> path[0], is the directory containing the script that was used to
> invoke the Python interpreter. If the script directory is not
> available (e.g. if the interpreter is invoked interactively or if
> the script is read from standard input), path[0] is the empty
> string, which directs Python to search modules in the current
> directory first. Notice that the script directory is inserted
> before the entries inserted as a result of PYTHONPATH.
>
> [...]
>
> ;)
>
> c
> --
> _B A U S T E L L E N_ lesen! --->> <
> http://www.blacktrash.org/baustellen.html>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20070207/d1f69e34/attachment-0003.html>