[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] Re: side effect problem of numpy.dot with Integer and QQ arrays.

2007-10-31 Thread William Stein
On Wed, 31 Oct 2007 21:53:35 -0700, Manny <[EMAIL PROTECTED]> wrote: > On Oct 30, 9:19 pm, Carl Witty <[EMAIL PROTECTED]> wrote: >> The simplest workaround is not to try to store Sage values in numpy >> arrays. Is there a reason you can't use Sage matrices? If there is >> some matrix functionali

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

2007-10-31 Thread Manny
On Oct 30, 9:19 pm, Carl Witty <[EMAIL PROTECTED]> wrote: > The simplest workaround is not to try to store Sage values in numpy > arrays. Is there a reason you can't use Sage matrices? If there is > some matrix functionality that numpy has and Sage doesn't, maybe we > could add it to Sage. Th

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

2007-10-30 Thread Carl Witty
On Oct 29, 12:05 am, Manny <[EMAIL PROTECTED]> wrote: > In sage, the arguments of numpy.dot can be changed when they > shouldn't. The following illustrates the problem: > > import numpy as npy > # With sage.rings.integer.Integer: > x = npy.array([1]) > print x > # [1] > npy.dot(x, npy.array([0])