Nick,
To the contrary, thanks for replying. I think the difference in my
situation is that bar() is being called by another method defined in
class A. This is returning "B" when I thought it would send back "A"
- mostly because I did not know/realize that class B even defined foo
(). Then I wa
Rob, Jason,
Sorry to quote wrong information! Having seen that Python issue rear
its ugly head, I thought it applied.
Nick
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sag
Nick and Jason,
Thanks for the replies.
> function. In this case, it seems like the best way to do things is to
> modify both the function in matrix2.pyx (for general matrices) and the
> function in matrix_rational_dense.pyx (for QQ matrices).
I was afraid that would be the answer. left_kerne
Nick Alexander wrote:
>> it would appear that that the call to kernel() in right_kernel() uses
>> the version of kernel() defined for dense rational matrices (as
>> perhaps it should), and not the modified version of left_kernel()
>> nearby (as the code locally might suggest one to expect).
>
> T
Rob Beezer wrote:
> I am trying to add some functionality to the matrix kernel routines
> (and I'm learning more about contributing to SAGE along the way).
> Briefly, I want to make some alternative bases possible as output. In
> matrix/matrix2.pyx, there are three methods defined for a matrix:
>
> it would appear that that the call to kernel() in right_kernel() uses
> the version of kernel() defined for dense rational matrices (as
> perhaps it should), and not the modified version of left_kernel()
> nearby (as the code locally might suggest one to expect).
The issue is with the kernel =
