Re: [Numpy-discussion] A couple more Numeric incompatibilitiesand a possible bug
![](https://secure.gravatar.com/avatar/e2eccf1773826049905a11f3f5c0e6a4.jpg?s=120&d=mm&r=g)
Hi Todd, Sorry if I wasn't clear. Yes, that's what I was expecting to see. Thanks for logging it and thanks for the explanation of why it's happening. I'd also like to restate the other issues in the email to which that one referred, which haven't been commented on. The cos function result
cos(1) 0.54030227661132813
gives a different result to cos(1.) Is this just because of numarray's stated departures from the way type coercion is done in Numeric? My guess is that numarray is casting the integer to a rank-0 Float32 array which is then coerced back to the native Python float type, which presumably is a float64 on the Windows platform. Do others think precision is being lost unnecessarily? Finally, has anyone got any comment about whether the __repr__ versus __str__ display of object array members is the expected behaviour? thanks, Gary -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm
![](https://secure.gravatar.com/avatar/faf9400121dca9940496a7473b1d8179.jpg?s=120&d=mm&r=g)
On Sun, 2004-03-28 at 19:46, Gary Ruben wrote:
This sounds correct. (Thanks for explaining it!)
Do others think precision is being lost unnecessarily?
No. Do you have any suggestions?
Finally, has anyone got any comment about whether the __repr__ versus __str__ display of object array members is the expected behaviour?
Yes. The basic look is exactly what I wanted:
But I'm open to suggestions and recognize that the handling of spaces/item sizing is weak (although it's not pronounced in this simple example). Do people want something else? Regards, Todd -- Todd Miller <jmiller@stsci.edu>
![](https://secure.gravatar.com/avatar/faf9400121dca9940496a7473b1d8179.jpg?s=120&d=mm&r=g)
On Sun, 2004-03-28 at 19:46, Gary Ruben wrote:
This sounds correct. (Thanks for explaining it!)
Do others think precision is being lost unnecessarily?
No. Do you have any suggestions?
Finally, has anyone got any comment about whether the __repr__ versus __str__ display of object array members is the expected behaviour?
Yes. The basic look is exactly what I wanted:
But I'm open to suggestions and recognize that the handling of spaces/item sizing is weak (although it's not pronounced in this simple example). Do people want something else? Regards, Todd -- Todd Miller <jmiller@stsci.edu>
participants (2)
-
Gary Ruben
-
Todd Miller