Re: mx.DateTime 3.2.x and numpy
V <[email protected]> Thu, 22 Dec 2011 17:15:45 +0000 (UTC)
| Newsgroups | gmane.comp.python.egenix.user |
|---|---|
| Message-ID | <[email protected]> |
Jim Vickroy <jim.vickroy@...> 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. Hi, Jim, According to numpy documentation, this is not in fact a bug, but desired behavior. Check out this link: http://docs.scipy.org/doc/numpy-1.6.0/reference/arrays.ndarray.html And specifically the relevant part of the documentation says: " 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. " _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users