Re: [Numpy-discussion] A couple more Numeric incompatibilitiesand apossible bug
![](https://secure.gravatar.com/avatar/e2eccf1773826049905a11f3f5c0e6a4.jpg?s=120&d=mm&r=g)
Thanks for pointing this out Alexander, I admit that I hadn't tried any native Python container types to see how they behave. I was basing my comments on Numeric's behaviour. When I have time, maybe I should raise a question on the Python developer's list. It seems like something that may have been overlooked. regards, Gary ----- Original Message ----- From: Alexander Schmolck <a.schmolck@gmx.net> Date: Mon, 29 Mar 2004 13:52:20 +0100 To: "numpy-discussion" <numpy-discussion@lists.sourceforge.net> Subject: Re: [Numpy-discussion] A couple more Numeric incompatibilitiesand apossible bug
"Gary Ruben" <gazzar@email.com> writes:
In summary, I think te behaviour should be
print str(ArrayOfErr([909., 802., 677., 585.], 1.0)) [909.0 +1.0/-1.0 802.0 +1.0/-1.0 677.0 +1.0/-1.0 585.0 +1.0/-1.0 ]
print repr(ArrayOfErr([909., 802., 677., 585.], 1.0)) ObjectArray([Err(909.0,1.0,1.0), Err(802.0,1.0,1.0), Err(677.0,1.0,1.0), Err(585.0,1.0,1.0)])
Such behavior would seem sensible, but I don't think it's what the builtin collections do (not sure why):
n = 1.1 n 1.1000000000000001 [n] [1.1000000000000001] str(n) '1.1' str([n]) '[1.1000000000000001]'
'as
-- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm
participants (1)
-
Gary Ruben