[sage-devel] Re: Glib algorithms #2436 vote

On Mar 26, 2008, at 4:48 PM, Gary Furnish wrote: > I have not yet benchmarked hash tables (nor actually tried them > out), but one of the big advantages is that they avoid much of the > memory management issues, so I don't expect them to be slower (and > if they are, I may have to fix that)

[sage-devel] Re: Glib algorithms #2436 vote

On Wed, 26 Mar 2008 11:57:26 -0700, Gary Furnish <[EMAIL PROTECTED]> wrote: > Honestly, independent of the spkg vs libcsage issue, which is really an > issue of semantics in my opinion, Sage has no high speed implementations of > C algorithms. Sage can not escape this forever. Either someone wi

[sage-devel] Re: mercurial --> plain text --> mercurial

On Wed, 26 Mar 2008 13:59:10 -0700, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > On Mar 26, 2008, at 1:56 PM, mabshoff wrote: > >> On Mar 26, 9:35 pm, Robert Bradshaw <[EMAIL PROTECTED]> >> wrote: >> >>> I was talking about something more sophisticated than export/import, >>> which won't work t

[sage-devel] Re: Glib algorithms #2436 vote

On Wed, 26 Mar 2008 14:06:08 -0700, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > On Mar 26, 2008, at 11:57 AM, Gary Furnish wrote: > >> Honestly, independent of the spkg vs libcsage issue, which is >> really an issue of semantics in my opinion, Sage has no high speed >> implementations of C alg

[sage-devel] Re: Glib algorithms #2436 vote

There are non trivial changes involved in getting compilation without internationalization, primarily because their error handling system uses internationalization in many places. Its not just a copy and paste job, but now that I've figured out exactly what headers we need and set up autoconf repl

[sage-devel] Re: sage question, possible contribution to project

No guilt. I feel no personal guilt over ancestors who owned slaves. Just a feeling it's worthwhile to contribute something more substantial that a few bug reports -- I guess meaning can get lost in ASCII. Some of us relatively new people feel like we're lost in a non-English megalopolis with no

[sage-devel] Re: mercurial --> plain text --> mercurial

Mike Hansen wrote: >> The queues feature in Mercurial is available independently in the >> quilt system. Mercurial makes this point: >> > > There are things with queues that you don't get with quilt. Quoting > from the book, > > "As an example, t

[sage-devel] Re: Sage 2.11.alpha1 released!

mabshoff wrote: > > > On Mar 26, 10:53 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: >> mabshoff wrote: >> >>> Well, maybe I did accidentally nuke more than the .svn directories. I >>> cannot imagine a scenario where anything would depend on the content >>> of a .svn directory to run. But I wouldn't

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 10:53 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > > Well, maybe I did accidentally nuke more than the .svn directories. I > > cannot imagine a scenario where anything would depend on the content > > of a .svn directory to run. But I wouldn't be surprised to be prov

[sage-devel] Winners of the "waste space on sage.math" contest March 2008

Hello folks, home on sage.math did just get filled up to the last byte, so things tend to work less well than they used to. Various people in IRC did clean up some of their home directories and now 26 GB are free again. But of the 705G total the following people use at least a Gigabyte: 1.9G

[sage-devel] Re: Sage 2.11.alpha1 released!

mabshoff wrote: > > > Well, maybe I did accidentally nuke more than the .svn directories. I > cannot imagine a scenario where anything would depend on the content > of a .svn directory to run. But I wouldn't be surprised to be proven > wrong ;) > I did a diff -r on both directories, only .svn

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 10:31 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > Hi folks, > > > Sage 2.11.alpha1 is out. It is a collection of various > > fixes, nothing particular seems to stand out. We finally > > pushed the updated experimental mayavi and vtl.spkg. > > [...] > > #2493: Jaap

[sage-devel] Re: Sage 2.11.alpha1 released!

mabshoff wrote: > Hi folks, > > Sage 2.11.alpha1 is out. It is a collection of various > fixes, nothing particular seems to stand out. We finally > pushed the updated experimental mayavi and vtl.spkg. > [...] > #2493: Jaap Spies: Updated experimental vtk spkg >(vtk-5.0.4.spkg) > #2495: J

[sage-devel] Re: Glib algorithms #2436 vote

On Mar 26, 2008, at 11:57 AM, Gary Furnish wrote: > Honestly, independent of the spkg vs libcsage issue, which is > really an issue of semantics in my opinion, Sage has no high speed > implementations of C algorithms. Sage can not escape this forever. > Either someone will have to write the

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 2008, at 1:56 PM, mabshoff wrote: > On Mar 26, 9:35 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: > >> I was talking about something more sophisticated than export/import, >> which won't work the instant one has multiple branches. One needs to >> actually create multiple heads, appl

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 9:35 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > I was talking about something more sophisticated than export/import,   > which won't work the instant one has multiple branches. One needs to   > actually create multiple heads, apply patches, then resolve them. Hg   > export doesn'

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 2008, at 1:30 PM, mabshoff wrote: > On Mar 26, 9:27 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: >> On Mar 26, 2008, at 11:53 AM, William Stein wrote: >> >> >> >>> Hi Jason (or anybody), >> >>> Does anybody have a clue if it is possible to take a directory >>> (e.g., >>> devel/sa

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 9:27 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > On Mar 26, 2008, at 11:53 AM, William Stein wrote: > > > > > Hi Jason (or anybody), > > > Does anybody have a clue if it is possible to take a directory (e.g., > > devel/sage/) with an .hg repo directory > > in it, and do the follo

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 2008, at 11:53 AM, William Stein wrote: > Hi Jason (or anybody), > > Does anybody have a clue if it is possible to take a directory (e.g., > devel/sage/) with an .hg repo directory > in it, and do the following: > > (1) export everything in the .hg repo to something (perhaps a ton of

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 11:53 am, "William Stein" <[EMAIL PROTECTED]> wrote: > Hi Jason (or anybody), > > Does anybody have a clue if it is possible to take a directory (e.g., > devel/sage/) with an .hg repo directory > in it, and do the following: > > (1) export everything in the .hg repo to something (perh

[sage-devel] Re: mercurial --> plain text --> mercurial

>> The queues feature in Mercurial is available independently in the >> quilt system. Mercurial makes this point: >> > >There are things with queues that you don't get with quilt. Quoting >from the book, > >"As an example, the integration of patche

[sage-devel] Re: hg churn and contributions

On Wednesday 26 March 2008 15:16, Craig Citro wrote: > Did we check in a big chunk of the ntl wrapper under your name? (That > one would be fair, of course). Or maybe when we moved libcsage into > the sage tree, that went in under your name? I suspect that both of these things are a big contribut

[sage-devel] Re: mercurial --> plain text --> mercurial

> The queues feature in Mercurial is available independently in the > quilt system. Mercurial makes this point: > There are things with queues that you don't get with quilt. Quoting from the book, "As an example, the integration of patches with r

[sage-devel] Re: Fast matrices over GF(p)

Dear all, i made a new version of my wrapper that is based on the most recent MeatAxe. You can find it at http://sage.math.washington.edu/home/SimonKing/MeatAxe.tar.gz The tar'd folder contains: - a part of the unaltered source files of MeatAxe 2.4, - additional (very simplistic) C-code in Mo

[sage-devel] Re: mercurial --> plain text --> mercurial

Mike, >Using queues has made me quite a bit more productive, and I'd like to >avoid switching to a version control system without them. Also, the >git documentation leaves something to be desired compared to the >Mercurial book. The queues feature in Mercurial is available independently in the

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 8:12 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Wed, Mar 26, 2008 at 1:18 PM, root <[EMAIL PROTECTED]> wrote: > > >  William, > > >  git can do this. Since git uses a hash it will always regenerate the > >  same hash from the same file. > > >  In fact, git uses hashes all the

[sage-devel] Re: mercurial --> plain text --> mercurial

It seems like the mercurial mailing list would be the best place to go for this. Using queues has made me quite a bit more productive, and I'd like to avoid switching to a version control system without them. Also, the git documentation leaves something to be desired compared to the Mercurial bo

[sage-devel] Re: hg churn and contributions

Did we check in a big chunk of the ntl wrapper under your name? (That one would be fair, of course). Or maybe when we moved libcsage into the sage tree, that went in under your name? -cc On Wed, Mar 26, 2008 at 12:02 PM, Joel B. Mohler <[EMAIL PROTECTED]> wrote: > > On Wednesday 26 March 2008 1

[sage-devel] Re: hg churn and contributions

On Wed, Mar 26, 2008 at 12:02 PM, Joel B. Mohler <[EMAIL PROTECTED]> wrote: > > On Wednesday 26 March 2008 13:55, Jason Grout wrote: > > Mercurial 1.0 is out now and one of the new standard extensions is the > > "churn" command, which apparently gives the numbers of lines of changed > > code p

[sage-devel] Re: mercurial --> plain text --> mercurial

On Wed, Mar 26, 2008 at 1:18 PM, root <[EMAIL PROTECTED]> wrote: > > William, > > git can do this. Since git uses a hash it will always regenerate the > same hash from the same file. > > In fact, git uses hashes all the way down the tree so you can just > look at the hash code of the root of

[sage-devel] Re: Sage Journal

On Mar 26, 10:33 am, "William Stein" <[EMAIL PROTECTED]> wrote: > > On Wed, 26 Mar 2008 09:32:36 -0700 (PDT) > > Harald Schilly <[EMAIL PROTECTED]> wrote: > > > I had the idea of publishing an online Journal with articles about > > > Sage - a mixture between blogs and a real journal. This coul

[sage-devel] Re: mercurial --> plain text --> mercurial

William, git can do this. Since git uses a hash it will always regenerate the same hash from the same file. In fact, git uses hashes all the way down the tree so you can just look at the hash code of the root of the tree to see if anything changes. Equal hash codes, even across the net, imply ex

[sage-devel] Re: mercurial --> plain text --> mercurial

On Mar 26, 7:53 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Hi Jason (or anybody), > > Does anybody have a clue if it is possible to take a directory (e.g., > devel/sage/) with an .hg repo directory > in it, and do the following: > >   (1) export everything in the .hg repo to something (per

[sage-devel] Re: hg churn and contributions

On Wednesday 26 March 2008 13:55, Jason Grout wrote: > Mercurial 1.0 is out now and one of the new standard extensions is the > "churn" command, which apparently gives the numbers of lines of changed > code per person (well, per email address). I thought the output (see > below) was interesting.

[sage-devel] Re: Glib algorithms #2436 vote

Honestly, independent of the spkg vs libcsage issue, which is really an issue of semantics in my opinion, Sage has no high speed implementations of C algorithms. Sage can not escape this forever. Either someone will have to write their own at some point or we can use glib as a starting block. It

[sage-devel] mercurial --> plain text --> mercurial

Hi Jason (or anybody), Does anybody have a clue if it is possible to take a directory (e.g., devel/sage/) with an .hg repo directory in it, and do the following: (1) export everything in the .hg repo to something (perhaps a ton of stuff) in plain text format, (2) delete .hg (3) do somethin

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 2008, at 11:07 , William Stein wrote: > > On Wed, Mar 26, 2008 at 11:05 AM, Justin C. Walker <[EMAIL PROTECTED]> > wrote: >> >> >> On Mar 26, 2008, at 10:37 , William Stein wrote: >>> >>> On Wed, Mar 26, 2008 at 9:15 AM, mabshoff >>> <[EMAIL PROTECTED]> wrote: >> [snip] >> Yeah,

[sage-devel] Re: [sage-support] Re: modular forms bug(s)?

Hey all, (I'm cc'ing this to sage-devel, because I think there are people there who care about modular forms who might not read sage-support.) So I've also posted a patch on #2674, which actually fixes both of these issues, as well as the fact that it currently is the case that adding an element

[sage-devel] Re: hg churn and contributions

On Wed, Mar 26, 2008 at 10:55 AM, Jason Grout <[EMAIL PROTECTED]> wrote: > > Mercurial 1.0 is out now and one of the new standard extensions is the > "churn" command, which apparently gives the numbers of lines of changed > code per person (well, per email address). I thought the output (see >

[sage-devel] Re: Glib algorithms #2436 vote

On Wed, Mar 26, 2008 at 11:16 AM, didier deshommes <[EMAIL PROTECTED]> wrote: > > > On Wed, Mar 26, 2008 at 1:52 PM, mabshoff > <[EMAIL PROTECTED]> wrote: > > > > > > > > On Mar 26, 6:43 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > > On Wed, Mar 26, 2008 at 10:09 AM, mabshoff > >

[sage-devel] Re: Sage Journal

On Mar 26, 6:33 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Wed, Mar 26, 2008 at 10:08 AM, Burcin Erocal <[EMAIL PROTECTED]> wrote: > >  Is it possible to call it Sage Monthly or Quarterly, so that it is not > >  confused with JSage? > > Yes, the name should either change as you suggest,..

[sage-devel] Re: Glib algorithms #2436 vote

On Wed, Mar 26, 2008 at 1:52 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Mar 26, 6:43 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > On Wed, Mar 26, 2008 at 10:09 AM, mabshoff > > > > > <[EMAIL PROTECTED]> wrote: > > > > > On Mar 26, 6:02 pm, "William Stein" <[EMAIL PROTECTED]> wr

[sage-devel] Get Paid to work on the Sage Notebook all Summer

Hi, If you are a student and would really like to get paid to work on the Sage Notebook all summer, go to this web page and fill out an application http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants Apply to the Python Software

[sage-devel] Re: another matrix() corner case for sparse matrices

On Wed, Mar 26, 2008 at 2:01 PM, Jason Grout <[EMAIL PROTECTED]> wrote: > > Ryan Hinton brought up a good point at #2651: > > Currently, matrix(3,{(1,1): 2}) gives the 3x2 sparse matrix > > [0 0] > [0 2] > [0 0] > > > However, for other cases, if we specify just the number of rows, the > re

[sage-devel] Re: Sage 2.11.alpha1 released!

On Wed, Mar 26, 2008 at 11:05 AM, Justin C. Walker <[EMAIL PROTECTED]> wrote: > > > On Mar 26, 2008, at 10:37 , William Stein wrote: > > > > On Wed, Mar 26, 2008 at 9:15 AM, mabshoff > > <[EMAIL PROTECTED]> wrote: > [snip] > > >> Yeah, but that mean that any Sage release that is supposed to w

[sage-devel] Re: another matrix() corner case for sparse matrices

On Wed, Mar 26, 2008 at 11:01 AM, Jason Grout <[EMAIL PROTECTED]> wrote: > > Ryan Hinton brought up a good point at #2651: > > Currently, matrix(3,{(1,1): 2}) gives the 3x2 sparse matrix > > [0 0] > [0 2] > [0 0] > > > However, for other cases, if we specify just the number of rows, the > r

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 2008, at 10:37 , William Stein wrote: > > On Wed, Mar 26, 2008 at 9:15 AM, mabshoff > <[EMAIL PROTECTED]> wrote: [snip] >> Yeah, but that mean that any Sage release that is supposed to work >> will so far only work up to 10.5.1. I didn't know that the tiny >> version number of OSX can

[sage-devel] Re: Sage Journal

Fantastic idea, Harald! Along these lines, how about a Sage User Group? We could hold it on Second Life or use Skype and screen sharing software. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group

[sage-devel] another matrix() corner case for sparse matrices

Ryan Hinton brought up a good point at #2651: Currently, matrix(3,{(1,1): 2}) gives the 3x2 sparse matrix [0 0] [0 2] [0 0] However, for other cases, if we specify just the number of rows, the returned matrix is square (except when we are giving all the entries of the matrix and there aren't

[sage-devel] hg churn and contributions

Mercurial 1.0 is out now and one of the new standard extensions is the "churn" command, which apparently gives the numbers of lines of changed code per person (well, per email address). I thought the output (see below) was interesting. This is as of 2.10.4 and a few extra patches on top of i

[sage-devel] Re: Glib algorithms #2436 vote

On Mar 26, 6:43 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Wed, Mar 26, 2008 at 10:09 AM, mabshoff > > <[EMAIL PROTECTED]> wrote: > > >  On Mar 26, 6:02 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > >  > Is any of the code gpl v3+ only? > > >  No. > > That's good. > > > > >  > How di

[sage-devel] Re: Sage 2.11.alpha1 released!

On Wed, Mar 26, 2008 at 9:15 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Mar 26, 4:43 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > > On Mar 26, 2008, at 24:27 , mabshoff wrote: > > > > > > > > Ok, this is the culprit. It will need fixes all over the place and > > > this time we

[sage-devel] Re: Glib algorithms #2436 vote

On Wed, Mar 26, 2008 at 10:09 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Mar 26, 6:02 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > Is any of the code gpl v3+ only? > > No. That's good. > > > > How difficult will it be to update our version whenever upstream > > changes? Do on

[sage-devel] Re: Sage Journal

On Wed, Mar 26, 2008 at 10:08 AM, Burcin Erocal <[EMAIL PROTECTED]> wrote: > > Hello, > > > On Wed, 26 Mar 2008 09:32:36 -0700 (PDT) > Harald Schilly <[EMAIL PROTECTED]> wrote: > > > I had the idea of publishing an online Journal with articles about > > Sage - a mixture between blogs and a re

[sage-devel] Re: Glib algorithms #2436 vote

On Mar 26, 6:02 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Is any of the code gpl v3+ only? No. > How difficult will it be to update our version whenever upstream > changes?  Do only you know how to do this? Not particularly hard. > Why put this in c_lib instead of a separate spkg call

[sage-devel] Re: Sage Journal

Hello, On Wed, 26 Mar 2008 09:32:36 -0700 (PDT) Harald Schilly <[EMAIL PROTECTED]> wrote: > I had the idea of publishing an online Journal with articles about > Sage - a mixture between blogs and a real journal. This could be an > excellent vehicle to promote Sage and the ideas behind to a bigge

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 5:53 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > On Mar 26, 2008, at 09:15 , mabshoff wrote: > > > > > On Mar 26, 4:43 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > >> On Mar 26, 2008, at 24:27 , mabshoff wrote: > [snip] > >>> Yeah, the culprit is the above regexp. I wil

[sage-devel] Re: Glib algorithms #2436 vote

Is any of the code gpl v3+ only? How difficult will it be to update our version whenever upstream changes? Do only you know how to do this? Why put this in c_lib instead of a separate spkg called glib-min? Couldn't such a package be useful outside of sage? Any chance the glib people might see

[sage-devel] Re: Glib algorithms #2436 vote

On Mar 25, 5:12 pm, Gary Furnish <[EMAIL PROTECTED]> wrote: > Trac #2436 adds the following algorithms from glib to libcsage: > Multiplatform threads > Thread pools > Asynchronous Queues > Memory Slices > Doubly and Singly linked lists > Queues > Sequences > Hash Tables > Arrays > Balanced Binary

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 2008, at 09:15 , mabshoff wrote: > > On Mar 26, 4:43 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: >> On Mar 26, 2008, at 24:27 , mabshoff wrote: [snip] >>> Yeah, the culprit is the above regexp. I will fix those before >>> 2.11.alpha2. Sorry for the mess. I made this #2672 - a blo

[sage-devel] Re: sage question, possible contribution to project

On Wednesday 26 March 2008 11:34, dean moore wrote: > At this link, we have, > >   Absolutely *everybody* who uses *Sage* should contribute something back > to *Sage* at some point. > > I have had my fun with sage, and debated, "How can I return someth

[sage-devel] Sage Journal

Hello all I had the idea of publishing an online Journal with articles about Sage - a mixture between blogs and a real journal. This could be an excellent vehicle to promote Sage and the ideas behind to a bigger audience. This could be about: * how to use Sage, explaining functionalities, ... *

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 4:43 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > On Mar 26, 2008, at 24:27 , mabshoff wrote: > > > > Ok, this is the culprit. It will need fixes all over the place and > > this time we might as well do it right. > > Oh, what the heck.  Do it wrong for a couple of more times :-

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 2008, at 24:27 , mabshoff wrote: > > On Mar 26, 5:45 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: >> >> On Mar 25, 2008, at 19:16 , mabshoff wrote: [snip] >>> more GMP trouble. Can you post the output from "uname -r | sed s/9\. >>> [0-9]\.0/9\.0\.0/" and a "uname -a". >> >> $ unam

[sage-devel] sage question, possible contribution to project

At this link, we have, Absolutely *everybody* who uses *Sage* should contribute something back to *Sage* at some point. I have had my fun with sage, and debated, "How can I return something to the community, however small?" I submitted a couple doc

[sage-devel] Re: Glib algorithms #2436 vote

On Wednesday 26 March 2008, Gary Furnish wrote: > Trac #2436 adds the following algorithms from glib to libcsage: > Multiplatform threads > Thread pools > Asynchronous Queues > Memory Slices > Doubly and Singly linked lists > Queues > Sequences > Hash Tables > Arrays > Balanced Binary Trees > N-ar

[sage-devel] Re: Glib algorithms #2436 vote

+1 --Mike On Tue, Mar 25, 2008 at 7:15 PM, <[EMAIL PROTECTED]> wrote: > > > > > On Tue, 25 Mar 2008, Gary Furnish wrote: > > > > > Trac #2436 adds the following algorithms from glib to libcsage: > > Multiplatform threads > > Thread pools > > Asynchronous Queues > > Memory Slices > > Dou

[sage-devel] Re: Request for Reviews, Reviews, Reviews!

On Tue, 25 Mar 2008 at 07:22PM -0700, mabshoff wrote: > But there are still plenty of patches in trac that deserve to be > looked at and merged. Might I recommend 2565? http://sagetrac.org/sage_trac/ticket/2565 The logging facilities currently are totally broken. The above ticket has a patch t

[sage-devel] Re: Sage 2.11.alpha1 released!

It started working after I installed atlas system wide. Atlas was not installed in the first attempt to compile sage. After linbox failed, my solution was to install atlas through gentoo package manager and try again. Cheers, Soroosh On Wed, Mar 26, 2008 at 3:36 AM, mabshoff < [EMAIL PROTECTED]>

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 3:25 am, "Soroosh Yazdani" <[EMAIL PROTECTED]> wrote: > Should I uninstall atlas if I want to check your patch for the future > version? Atlas is installed system wide on my computer, and linbox seemed to > have found those libraries as it compiled afterward. Is there a way to force >

[sage-devel] Re: Sage 2.11.alpha1 released!

On Mar 26, 5:45 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > Hi, Hichael, > > On Mar 25, 2008, at 19:16 , mabshoff wrote: > > > > > > > On Mar 26, 2:58 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > >> On Mar 22, 2008, at 16:02 , mabshoff wrote: > >>>http://sage.math.washington.edu/h