Mr. M wrote:
> Somehow, the bug does not show up any more. I believe it was due to the
> numpy version that is fetched by cPickle. Is there any way to control
> (or even determine), which library version cPickle grabs for unpickling
> a numpy array (numpy, scipy, etc)?
You can import the appro
Martin Manns wrote:
> Robert Kern wrote:
>> Martin Manns wrote:
>
>>> If I cPickle a numpy array under Linux and un-cPickle it under Solaris
>>> 10, my arrays seem to be transposed.
>> Transposed? That's odd. There was a byteorder issue with pickles going across
>> differently-endianed platforms
Robert Kern wrote:
> Martin Manns wrote:
>> If I cPickle a numpy array under Linux and un-cPickle it under Solaris
>> 10, my arrays seem to be transposed.
> Transposed? That's odd. There was a byteorder issue with pickles going across
> differently-endianed platforms that was fixed in the past fe
Martin Manns wrote:
> Hi
>
> If I cPickle a numpy array under Linux and un-cPickle it under Solaris
> 10, my arrays seem to be transposed. Is there any way to get the same
> behavior on both platforms without testing which platform the python
> script runs on and then transposing the array?
>
> I
Hi
If I cPickle a numpy array under Linux and un-cPickle it under Solaris
10, my arrays seem to be transposed. Is there any way to get the same
behavior on both platforms without testing which platform the python
script runs on and then transposing the array?
I am using python 2.4.2 and numpy 0.9
