On Nov 11, 12:07 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> On Nov 11, 12:02 pm, John H Palmieri <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Nov 11, 11:57 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> > > John H Palmieri wrote:
> > > > On Nov 11, 4:24 am, mabshoff <[EMAIL PROTECTED]> wrote:
> > > >> Hello folks,
>
> > > >> here is 3.2.rc0 and I have to confess that I cheated: I did build this
> > > >> on numerous platforms before announcing here (if you hung out in IRC
> > > >> you knew about this release for about 6 hours now) and as it turns out
> > > >> my caution was justified. Doctesting is broken with this release
> > > >> unless you do the following:
>
> > > >>  ./sage -sh
> > > >>  cd local/bin
> > > >>  hg update -C
>
> > > > When I try to do the last line (on an intel mac running 10.5), I get
> > > > this:
>
> > > > abort: could not import module lookup!
>
> > > > Did I do something wrong?
>
> > > do:
>
> > > ./sage -sh
> > > cd local/bin
> > > ./hg update -C
>
> > Here's what happens:
>
> > (/Applications/sage) [11:26am]>> ./sage -sh
>
> > Starting subshell with Sage environment variables set.
> > Be sure to exit when you are done and do not do anything
> > with other copies of Sage!
>
> So far so good.
>
> > (/Applications/sage) [11:58am]>> cd local/bin
> > (...local/bin) [11:58am]>> ./hg update -C
> > abort: could not import module lookup!
>
> mmh - can you try without the "./" since hg is in $PATH.

I did that first, same problem.

> What shell
> are you using - even though this should not matter, but one never
> knows.

Oh, this is the problem.  I'm running tcsh (I got used to it years
ago, and keep deciding it's too much work to switch).  When I switch
to bash, everything works.


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to