[sage-support] Re: segment fault in Singular-- return error?

2007-11-02 Thread mabshoff
[CC to Hannes Schönemann] On Nov 3, 7:05 am, Ursula Whitcher <[EMAIL PROTECTED]> wrote: Hello Ursula, Hannes, I can reproduce this issue with the Singular shipped with Sage 2.8.11, but originally it happened with Sage 2.8.10, also. The log is from sage.math, i.e. and x86-64 Linux box. > Willia

[sage-support] Re: segment fault in Singular-- return error?

2007-11-02 Thread Ursula Whitcher
William Stein wrote: > Do you use a funny shell, have funny environment variables > set, load customizations? ... becomes root on sage.math > and tries your session as you... and it works fine. > Maybe you didn't paste the correct log into your email. > Please try replicating it yourself, so you

[sage-support] Re: side effect problem of numpy.dot with Integer and QQ arrays.

2007-11-02 Thread Manny
On Oct 31, 11:40 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > numpy arrays are multidimensional, etc., and are much more sophisticated > than Sage matrices. All Sage does is 2-dimensional nxm matrices, and > isn't really designed for sophisticated reshaping, especially in the > multidimensio

[sage-support] There is now a Sage tax-deductible donation account

2007-11-02 Thread William Stein
Hello, I just wanted to let everybody know Sage received > $1000 in donations recently, so I was able to have the University of Washington setup a special account for Sage. Now anybody can easily make tax-deductible donations to be used to support Sage development. I put a link to the "UW dona

[sage-support] Re: [sage-devel] Re: numpy vs. in-place optimizations

2007-11-02 Thread William Stein
On 11/2/07, Dan Christensen <[EMAIL PROTECTED]> wrote: > numpy arrays are extremely flexible, with broadcasting, view semantics > and in-place operations being the most important reason why. For > example, if x is an array, then x[3:5] is a view of part of x, and > I can adjust the entries in jus

[sage-support] Re: numpy vs. in-place optimizations

2007-11-02 Thread Dan Christensen
Robert Bradshaw <[EMAIL PROTECTED]> writes: > This is due to the inplace operator stuff using refcounts to > determine if it's safe to mutate. The simple workaround is to not use > numpy arrays of SAGE objects. Another question is why would one do so > (i.e. what is lacking in the SAGE line

[sage-support] Re: problem installing SAGE 2.8.10

2007-11-02 Thread didier deshommes
On 11/2/07, Paul Zimmermann <[EMAIL PROTECTED]> wrote: > I take the opportunity to ask why the unknown 'x' is special in Sage: Mostly convenience since most people use x for a polynomial or the name of a variable. In earlier versions x was defined to be the polynomial x, now it's a symbolic varia

[sage-support] Re: problem installing SAGE 2.8.10

2007-11-02 Thread Paul Zimmermann
> The culprit is NTL: > > powerpc-apple-darwin8-g++-4.0.1: unrecognized option '-shared' > /usr/bin/ld: Undefined symbols: > _main > ___gmpn_add_n > ___gmpn_addmul_1 > [...] > collect2: ld returned 1 exit status > make[3]: *** [libntl.so] Error 1 > make[2]: *** [lib] Error 2 > ---