On Wed, 2012-05-23 at 17:31 -0500, Nathaniel Smith wrote:
On Wed, May 23, 2012 at 10:53 PM, Travis Oliphant tra...@continuum.io wrote:
To be clear, I'm not opposed to the change, and it looks like we should go
forward.
In my mind it's not about developers vs. users as satisfying users
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
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
EPD.
Best regards,
Michael
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
--
--
Kathleen M. Tacina
NASA Glenn Research
on the platform?
My 2 cents,
eat
--
--
Kathleen M. Tacina
NASA Glenn Research Center
MS 5-10
21000 Brookpark Road
Cleveland, OH 44135
Telephone: (216) 433-6660
Fax: (216) 433-5802
I get the following runtime error when I import numpy: module compiled
against ABI version 200 but this version of numpy is 109 (see
below).
Python 2.7.1 (r271:86832, May 20 2011, 14:41:42)
[GCC 4.4.0 20090514 (Red Hat 4.4.0-6)] on linux2
Type help, copyright, credits or license for more
Hi,
I've been finding numpy/scipy/matplotlib a very useful tool for data
analysis. However, a recent change has caused me some problems.
Numpy used to allow the name and title of a column of a structured array
or recarray to be the same (at least in the svn version as of early last
winter).