Hi there,
currently, MatrixSpace's zero_matrix command is implemented as follows:
@cached_method
def zero_matrix(self):
res = self.__matrix_class(self, 0, coerce=False, copy=False)
res.set_immutable()
return res
which means that whenever on calls matrix(K,m,n) for the first time, it
creates two matrices which is a very very bad idea when working with big
matrices (== RAM full)
I found
http://trac.sagemath.org/sage_trac/ticket/8276
and a few discussions about it on [sage-devel]. However, all those discussions
seem to assume that caching zero_matrix() is a good idea. Hence, I wonder if I
just missed the discussion or the reason on this?
In any case, there should at least be an option to disable this (say after
certain dimensions)?
Cheers,
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
_www: http://martinralbrecht.wordpress.com/
_jab: martinralbre...@jabber.ccc.de
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
