[SciPy-dev] Is this a (formatting) bug?
David Goldsmith
d_l_goldsmith at yahoo.com
Fri Jul 3 01:22:02 EDT 2009
I figured out a "work-around":
>>> w,v=LA.eig(np.diag((1,2,3)))
>>> w;v
array([ 1., 2., 3.])
array([[ 1., 0., 0.],
[ 0., 1., 0.],
[ 0., 0., 1.]])
But I'm still "concerned" about how >>> w,v (effectively) is printed (though I now see more clearly that it's an artifact of how a tuple is printed, not an artifact of how LA.eig is printed, and thus probably "unfixable" solely within numpy).
DG
--- On Thu, 7/2/09, David Goldsmith <d_l_goldsmith at yahoo.com> wrote:
> From: David Goldsmith <d_l_goldsmith at yahoo.com>
> Subject: [SciPy-dev] Is this a (formatting) bug?
> To: scipy-dev at scipy.org
> Date: Thursday, July 2, 2009, 10:08 PM
>
> Actual output:
>
> >>> from numpy import linalg as LA
> >>> LA.eig(np.diag((1,2,3)))
> (array([ 1., 2., 3.]), array([[ 1.,
> 0., 0.],
> [ 0., 1., 0.],
> [ 0., 0.,
> 1.]]))
>
> i.e., a line feed wasn't inserted between w and v.
>
> Bug?
>
> DG
>
>
>
> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
More information about the SciPy-Dev
mailing list