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
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 just
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 linear
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
multidimensional
[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.
William
