Thanks!
It was interesting to see why that happened.
Kathy
On Tue, 2012-01-24 at 18:56 -0600, Mark Wiebe wrote:
On Tue, Jan 24, 2012 at 7:29 AM, Kathleen M Tacina
kathleen.m.tac...@nasa.gov wrote:
I was experimenting with np.min_scalar_type to make sure it
worked as
I was experimenting with np.min_scalar_type to make sure it worked as
expected, and found some unexpected results for integers between 2**63
and 2**64-1. I would have expected np.min_scalar_type(2**64-1) to
return uint64. Instead, I get object. Further experimenting showed
that the largest
I get the same results as you, Kathy.
*surprised*
(On OS X (Lion), 64 bit, numpy 2.0.0.dev-55472ca, Python 2.7.2.
On 24.01.2012, at 16:29, Kathleen M Tacina wrote:
I was experimenting with np.min_scalar_type to make sure it worked as
expected, and found some unexpected results for integers
On Tue, Jan 24, 2012 at 7:29 AM, Kathleen M Tacina
kathleen.m.tac...@nasa.gov wrote:
**
I was experimenting with np.min_scalar_type to make sure it worked as
expected, and found some unexpected results for integers between 2**63 and
2**64-1. I would have expected np.min_scalar_type(2**64-1)
