> Try doing
>
> sage: hg_scripts.merge()
> sage: hg_scripts.commit()
>
> and answer any interactive questions.
This doesn't seem to do anything:
sage: hg_scripts.merge()
cd "/pkgs/sage-2.7.1/local/bin" && hg merge
abort: there is nothing to merge - use "hg update" instead
sage: hg_scripts.comm
On Nov 22, 2007 7:17 AM, Nathan Dunfield <[EMAIL PROTECTED]> wrote:
> I encountered the following minor bug while upgrading to 2.8.13,
> namely the file
>
> $SAGEROOT/local/bin/sage-banner
>
> was not updated. So when I started sage after doing "sage -upgrade"
> it claimed that I was still on 2.
Hello folks,
now that 2.8.13 is out it is time to get the ball rolling on the
2.8.14 release. It is the thanksgiving weekend in the states, so we
might experience a little slowdown this time. There are plenty of
patches and open issues for 2.8.14, see
http://www.sagetrac.org/sage_trac/query?stat
On Nov 22, 2007 5:12 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> On Nov 22, 2007 5:20 AM, mabshoff
> <[EMAIL PROTECTED]> wrote:
> > > : libcsage.so: cannot open shared
> > > object file: No such file or directory
> > >
> > >
> > > So I think it's better to build it from source, right?
> >
>
> The time has everything to do with filesystem speed (and sytem load),
> and very little to do with CPU speed. It literally takes only a few seconds
> on most unloaded modern systems with a good hard drive, since all it
> is doing is looking at a bunch of files and in some cases making some
> ch
I'm acutely interested in this. I'm doing my senior thesis on the generation
of finite groups, and simple lie groups play a big role in this.
On Thu, 22 Nov 2007, Robert Miller wrote:
>
> I am interested in this, but it might be a while before I get some
> spare time to look at it.
>
> On Nov
I am interested in this, but it might be a while before I get some
spare time to look at it.
On Nov 21, 11:56 am, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> On Nov 21, 8:50 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> Hello David,
>
> > I think this is interesting but I wonder how eas
On Nov 22, 2007 5:20 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
> > : libcsage.so: cannot open shared
> > object file: No such file or directory
> >
> >
> > So I think it's better to build it from source, right?
>
> libcsage.so is missing in the binary, "sage -b" fixes that.
That's very weird. In
Is it possible to implement a progress meter for -upgrade? I've never seen
something like that with a compiling process, but why is that so?
On Nov 22, 2007 4:52 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> On Nov 22, 2007 7:42 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > On Nov 22, 2
On Nov 22, 2007 7:42 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> On Nov 22, 2007 1:37 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> > > so startup + relocation takes 12 seconds. So there are maybe some
> > > problems on your end :(
> >
> > I downloaded the binary version: sage-2.8.13-i686-Li
On Nov 22, 2007 7:31 AM, David Harvey <[EMAIL PROTECTED]> wrote:
> > You should make an AbstractAbelianGroup class that derives from
> > ParentWithBase.
>
> Hmmm but wouldn't it make more sense for AbelianGroup (i.e. the
> currently implemented one) to derive from AbstractAbelianGroup?
Yes, i
On Nov 22, 2007 1:37 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> > so startup + relocation takes 12 seconds. So there are maybe some
> > problems on your end :(
>
> I downloaded the binary version: sage-2.8.13-i686-Linux-debian32.tar.gz
>
> I tried that on my laptop and it indeed took only 57s,
On Nov 22, 2007, at 10:25 AM, William Stein wrote:
>
> On Nov 22, 2007 6:53 AM, David Joyner <[EMAIL PROTECTED]> wrote:
> \> On Nov 22, 2007 9:35 AM, David Harvey
> <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi all,
>>>
>>> I'd like to discuss this abelian group thing a bit further, from the
>>> point
On Nov 22, 2007 6:53 AM, David Joyner <[EMAIL PROTECTED]> wrote:
\> On Nov 22, 2007 9:35 AM, David Harvey <[EMAIL PROTECTED]> wrote:
> >
> > Hi all,
> >
> > I'd like to discuss this abelian group thing a bit further, from the
> > point of view of design issues rather than algorithms.
> >
> > Curre
I encountered the following minor bug while upgrading to 2.8.13,
namely the file
$SAGEROOT/local/bin/sage-banner
was not updated. So when I started sage after doing "sage -upgrade"
it claimed that I was still on 2.8.8.1:
PBook ~ (12) sage
--
On Nov 22, 2007 9:35 AM, David Harvey <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I'd like to discuss this abelian group thing a bit further, from the
> point of view of design issues rather than algorithms.
>
> Currently in SAGE the situation appears to be the following. An
> AbelianGroup represen
Hi all,
I'd like to discuss this abelian group thing a bit further, from the
point of view of design issues rather than algorithms.
Currently in SAGE the situation appears to be the following. An
AbelianGroup represents a (not necessarily finite) abelian group
whose structure is *known*; i
Hi all,
I'd like to discuss this abelian group thing a bit further, from the
point of view of design issues rather than algorithms.
Currently in SAGE the situation appears to be the following. An
AbelianGroup represents a (not necessarily finite) abelian group
whose structure is *known*; i
On Nov 22, 1:46 pm, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> on sage.math, am I supposed to use:
>
> http://sagemath.org/SAGEbin/linux/64bit/sage-2.8.13-x86_64-use_this_o...
>
> ? I tried that and this is what I got:
>
> $ wgethttp://sagemath.org/SAGEbin/linux/64bit/sage-2.8.13-x86_6
Hi,
on sage.math, am I supposed to use:
http://sagemath.org/SAGEbin/linux/64bit/sage-2.8.13-x86_64-use_this_only_on_the_computer_sage_dot_math-Linux.tar.gz
? I tried that and this is what I got:
$ wget
http://sagemath.org/SAGEbin/linux/64bit/sage-2.8.13-x86_64-use_this_only_on_the_computer_sa
> so startup + relocation takes 12 seconds. So there are maybe some
> problems on your end :(
I downloaded the binary version: sage-2.8.13-i686-Linux-debian32.tar.gz
I tried that on my laptop and it indeed took only 57s, which is less
than a minute. So there are probably some problems on my end.
On Nov 22, 12:12 pm, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
> Hi,
Hi Ondrej,
>
> I just downloaded the 2.8.13 version and it says:
>
> $ ./sage
> --
> | SAGE Version 2.8.13, Release Date: 2007-11-21 |
Hi,
I just downloaded the 2.8.13 version and it says:
$ ./sage
--
| SAGE Version 2.8.13, Release Date: 2007-11-21 |
| Type notebook() for the GUI, and license() for information.|
And Sage also already contains not one but two implementations of Weil
pairing (via Tate pairing) written by me, one version within mwrank
and the other in gp scripts.
The latter could easily be wrapped into Sage, but has not apparently been done.
In the same code there is more useful functional
24 matches
Mail list logo
