Emanuele Olivetti wrote:
> I'm running numpy 1.0 and 1.0.1 on several hosts and
> today I've found that pickling arrays in 1.0.1 generates
> problems to 1.0. An example:
> --- numpy 1.0.1 ---
> import numpy
> import pickle
> a = numpy.array([1,2,3])
> f=open('test1.pickle','w')
> pickle.dump(a,f)
>
On Thu, December 7, 2006 6:42 pm, Charles R Harris wrote:
> The 1.0.x versions are supposed to be compatible. I don't see any changes
> to
> pickle in svn since before the 1.0 release, so there might be another
> problem here. Are there other differences between the machines? Python
> version, OS,
Robert wrote:
> Robert Kern wrote:
>> numpy requires Python 2.3 .
>
> hope Python2.3 support will not be dropped too early. There is not much cost
> overall when going from 2.2 to 2.3.
It won't.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that
On 11/23/06, Jerome Fuselier <[EMAIL PROTECTED]> wrote:
Hello,
I've discovered a small problem when I tried to save a numpy array with
the pickle module. The dumped array is not always equal to the loaded one
and the error is not always here, depending on the way I express matrix
operations.
On 12/7/06, Keith Goodman <[EMAIL PROTECTED]> wrote:
On 12/7/06, Keith Goodman <[EMAIL PROTECTED]> wrote:
> On 12/7/06, Emanuele Olivetti <[EMAIL PROTECTED]> wrote:
> > How can I let access pickled arrays made in numpy 1.0.1 to numpy 1.0 ?
>
> If you pickle in 1.0.1, I bet you can read it in 1.0
On 12/7/06, Keith Goodman <[EMAIL PROTECTED]> wrote:
> On 12/7/06, Emanuele Olivetti <[EMAIL PROTECTED]> wrote:
> > How can I let access pickled arrays made in numpy 1.0.1 to numpy 1.0 ?
>
> If you pickle in 1.0.1, I bet you can read it in 1.0.
>
> I don't know why the pickle format keeps changing.
On 12/7/06, Emanuele Olivetti <[EMAIL PROTECTED]> wrote:
> How can I let access pickled arrays made in numpy 1.0.1 to numpy 1.0 ?
If you pickle in 1.0.1, I bet you can read it in 1.0.
I don't know why the pickle format keeps changing. But I understand
why an old version of software can't always r
Hi,
I know that numarray is outdated now, but it's too big a job to change
to numpy right now. On the offchance that someone can help:
After upgrading from numarray-1.3.1 to numarray-1.5.2, we get occasional
crashes where python tries to free Py_NONE
I'm aware of the NA_FromDimsStridesDescrAndDa
El dj 07 de 12 del 2006 a les 16:50 +0100, en/na Alexandre Fayolle va
escriure:
> Hi,
>
> I'm facing a memory leak on an application that has to use numarray and
> Numeric (because of external dependencies).
>
> The problem occurs when building a Numeric array from a numarray array:
>
> import
Robert Kern wrote:
> David Bogen wrote:
>> All:
>>
>> Is it possible to build Numpy using Python 2.2? I haven't been able to
>> find anything that explicitly lists the versions of Python with which
>> Numpy functions so I've been working under the assumption that the two
>> bits will mesh together
Hi,
I'm facing a memory leak on an application that has to use numarray and
Numeric (because of external dependencies).
The problem occurs when building a Numeric array from a numarray array:
import Numeric
import numarray
import sys
atest = numarray.arange(200)
temp = Numeric.array(atest)
pri
El dj 07 de 12 del 2006 a les 11:36 +0100, en/na Giorgio Luciano va
escriure:
> Does it exist a workaround for that to make numpy understand when an
> array is empty ?
> Giorgio
>
I guess there should be many. One possibility is to use .size:
In [9]:a=numpy.array([])
In [10]:a.size == False
Out
> Today's Topics:
>
>1. Re: equivalent to isempty command in matlab (newbie question)
> (Robert Kern)
>
>
> --
>
> Message: 1
> Date: Wed, 06 Dec 2006 11:20:19 -0600
> From: Robert Kern <[EMAIL PROTECTED]>
> Subject
I'm running numpy 1.0 and 1.0.1 on several hosts and
today I've found that pickling arrays in 1.0.1 generates
problems to 1.0. An example:
--- numpy 1.0.1 ---
import numpy
import pickle
a = numpy.array([1,2,3])
f=open('test1.pickle','w')
pickle.dump(a,f)
f.close()
---
If I unpickle test1.pickle in
14 matches
Mail list logo