> Aha! I am new at python and misunderstood how hg was working. All the > file "hg" does is import stuff from python, so it doesn't matter which > copy of hg I use, it matters which copy of python. The debian > supplied hg is broken, but the sage-2.6 version of hg works fine. > > Sorry for misidentifying the problem earlier!
Definitely feel free to send me an hg patch to the SAGE documentation that clarifies this issue in a way that might have been helpful to you if it had been there. Thanks. -- William -- Regarding Fortran, Josh Kantor spent all day working on using g95 instead of gfortran, and things are looking very very good. One nice thing is that g95 binaries are only 2-3MB each, so we can very reasonably include binaries for all of OS X PPC, Intel, and Linux (32 and 64-bit) in the standard SAGE tarball for 12MB (so no net access is needed when building SAGE). There are also very easy to get g95 binaries for a huge range of machines at http://ftp.g95.org/, so I'm happier with g95 over gfortran. -- William --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
