I made a similar message (on kubuntu) go away by editing /etc/mercurial/hgrc.d/hgext.rc putting a # (comment) at the start of the line which mentioned themissing package.
John On 9/23/07, cwitty <[EMAIL PROTECTED]> wrote: > > On Sep 20, 11:46 am, Jason Grout <[EMAIL PROTECTED]> wrote: > > 1. When I make changes to, say, devel/sage-branch/sage/graphs/graph.py, > > I don't see those changes available in SAGE. For example, I added a > > function to the Graph class, but I couldn't access that function when I > > started up SAGE. Eventually I accidentally did "sage -b branch", which > > looked like it copied and recompiled the graph.py file in the build > > directory and my changes worked fine. To see changes that I make in the > > source files, is that the proper procedure? (i.e., do sage -b branch > > before launching sage, even though devel/sage already points to > > sage-branch?) > > > > 2. Something seems wrong with my mercurial installation. I can't figure > > out where something might be misconfigured, though. I get errors about > > hgext/hct when using hg_sage inside of sage, but when running hg outside > > of sage, everything seems fine. I can find hct.py in > > /usr/local/lib/python2.5/site-packages/hgext/. Does anyone have any > > idea where I can poke to find out what's wrong? I'm running Ubuntu. > ... > > cd "/home/grout/sage/sage-2.8.3/devel/sage" && hg status > > *** failed to import extension hgext/hct: No module named hgext/hct > > *** failed to import extension hgext/hct: No module named hgext/hct > ... > > This is (a slightly different variant of) TRAC #310. > > The problem is that your local Ubuntu mercurial installation reads its > configuration information from /etc/mercurial, and looks for mercurial > extension packages in /usr/local/lib/python2.5/site-packages/hgext. > Your SAGE-specific mercurial installation, in your sage directory, > reads its configuration information from /etc/mercurial (same as > before) but looks for mercurial extension packages in .../sage/local/ > lib/python2.5/hgext. Your Ubuntu mercurial installation put something > in /etc/mercurial that says to use the hct extension package; but your > SAGE copy of mercurial doesn't have that package available. > > The simplest "workaround" is to simply ignore the error messages; they > don't seem to hurt anything. Less simple workarounds would include > editing the appropriate file under /etc/mercurial to avoid requiring > that extension, or installing the hct extension in SAGE's copy of > mercurial (perhaps copying the hct.py file suffices). The fix is > probably to change SAGE's mercurial to not pay attention to /etc/ > mercurial. > > Carl > > > > > -- John Cremona --~--~---------~--~----~------------~-------~--~----~ 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
