![](https://secure.gravatar.com/avatar/a2c89176be1b312d6d648616731557e2.jpg?s=120&d=mm&r=g)
it seems like the boolean result of the expression ( middle try ) causes a problem? thanks, Stefan Kuzminski ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
![](https://secure.gravatar.com/avatar/faf9400121dca9940496a7473b1d8179.jpg?s=120&d=mm&r=g)
On Fri, 2005-08-26 at 13:24, Stefan Kuzminski wrote:
This issue has been discussed before and the general consensus was that this (somewhat treacherous) behavior should not change. For array totals (reducing on all axes at once), numarray has a sum() method which by default does do a type promotion to the "max type of kind", so integers -> Int64, floats -> Float64, and complexes -> Complex64 prior to the reduction. Regards, Todd
![](https://secure.gravatar.com/avatar/faf9400121dca9940496a7473b1d8179.jpg?s=120&d=mm&r=g)
On Fri, 2005-08-26 at 13:24, Stefan Kuzminski wrote:
This issue has been discussed before and the general consensus was that this (somewhat treacherous) behavior should not change. For array totals (reducing on all axes at once), numarray has a sum() method which by default does do a type promotion to the "max type of kind", so integers -> Int64, floats -> Float64, and complexes -> Complex64 prior to the reduction. Regards, Todd
participants (2)
-
Stefan Kuzminski
-
Todd Miller