On Thu, Aug 2, 2012 at 3:13 PM, Robert Kern wrote:
> On Thu, Aug 2, 2012 at 11:41 PM, Geoffrey Irving wrote:
>> On Thu, Aug 2, 2012 at 1:26 PM, Robert Kern wrote:
>>> On Thu, Aug 2, 2012 at 8:46 PM, Geoffrey Irving wrote:
Hello,
The attached .npy file was written from custom C++
On Thu, Aug 2, 2012 at 11:41 PM, Geoffrey Irving wrote:
> On Thu, Aug 2, 2012 at 1:26 PM, Robert Kern wrote:
>> On Thu, Aug 2, 2012 at 8:46 PM, Geoffrey Irving wrote:
>>> Hello,
>>>
>>> The attached .npy file was written from custom C++ code. It loads
>>> fine in Numpy 1.6.2 with Python 2.6 ins
On Thu, Aug 2, 2012 at 1:26 PM, Robert Kern wrote:
> On Thu, Aug 2, 2012 at 8:46 PM, Geoffrey Irving wrote:
>> Hello,
>>
>> The attached .npy file was written from custom C++ code. It loads
>> fine in Numpy 1.6.2 with Python 2.6 installed through MacPorts, but
>> fails on a different machine wit
On Thu, Aug 2, 2012 at 8:46 PM, Geoffrey Irving wrote:
> Hello,
>
> The attached .npy file was written from custom C++ code. It loads
> fine in Numpy 1.6.2 with Python 2.6 installed through MacPorts, but
> fails on a different machine with Numpy 2.0.0 installed via Superpack:
>
> box:array% which
Hello,
The attached .npy file was written from custom C++ code. It loads
fine in Numpy 1.6.2 with Python 2.6 installed through MacPorts, but
fails on a different machine with Numpy 2.0.0 installed via Superpack:
box:array% which python
/usr/bin/python
box:array% which python
box:array% python
Py