[egenix-users] Re: mx.DateTime 3.2.x and numpy
jim.vickroy at noaa.gov
Thu Dec 22 13:52:04 CET 2011
On Thu, Dec 22, 2011 at 10:57 AM, V <vovansim at gmail.com> wrote:
> Jim Vickroy <jim.vickroy at ...> writes:
> > For what it is worth, as a mere "lurker" on this list,
> > that is an error in the numpy implementation, and should be reported.
> > My search attempts to find information on a justification for this
> > behavior are so far unsuccessful.
> Hmm, gmane seems to have swallowed my previous couple attempts to send a
> response... Perhaps it got labeled as spam due to inclusion of a link to
> documentation. Aany way,
> Jim, I believe that this is not actually a bug in numpy, but rather desired
> behavior. Documentation for numpy.ndarray.__float__ includes the following
> Conversion; the operations complex, int, long, float, oct, and hex.
> They work only on arrays that have one element in them and return
> the appropriate scalar.
> Thanks for this information -- and good detective work to diagnose the
I do think, however, this is an unfortunate numpy design decision. I would
rather __float__ not be provided at all since it only behaves as expected
for a trivial corner case. This is, to me, very unintuitive.
> eGenix.com User Mailing List http://www.egenix.com/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the egenix-users