Updates:
Cc: [email protected]
Comment #1 on issue 3495 by [email protected]: Matrices .args and .shape
should contain SymPy types
http://code.google.com/p/sympy/issues/detail?id=3495
There might be some reason why this is hard to do in explicit matrices. A
note from that PR from smichr:
It didn't fall on deaf ears...my thoughts then were, in response to why the
following was done in sympy/matrices/immutable.py:
@@ -39,24 +39,26 @@ def new(cls, *args, **kwargs):
@property
def shape(self):
return self.args[:2]
return tuple([int(i) for i in self.args[:2]])
I said,
Because that is what the other matrices return. So until they all derive
from Basic, I would like them all to give their properties in the same way.
For those that are hashed, creating an object with ints or Integers is
going to affect hashing...but if mutable ends up not being hashed then this
is a mute point. But...there are tests that fail if mutable's hash is
removed because of the custom eq, I believe. (If you defined eq then you
need a hash, as I recall.) So...for the time being I want to make sure that
what is expected from others is the same here.
So if they all behave the same, that's fine. Then the test in test_args (if
there is one) can be changed. And should the lists be Tuples (hence all the
row and column vectors be changed to return Tuples, too)?
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy-issues?hl=en.
