Brian Blais wrote:
> Would this break previously saved pickles, so you couldn't load them? I ran
> into
> that problem last year when there was a change to numpy. Is that something
> that
> would happen here?
No.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a h
> Would this break previously saved pickles, so you couldn't load them? I ran
into
> that problem last year when there was a change to numpy. Is that something
that
> would happen here?
>
> bb
>
Regardless of whether or not this change will "break pickles", it seems hi
On 1/31/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> To me this is so obvious that I don't understand the resistance in the
> Python community to the concept.
Indeed
Travis, I was not reading this for a some time ago. Can you point me
your last proposal? I remember reading about extending the
On Thu, Feb 01, 2007 at 05:51:22PM -0700, Travis Oliphant wrote:
> Christopher Barker wrote:
>
> >Travis Oliphant wrote:
> >
> >
> >>I'm thinking that we should have several. For example all the fromXXX
> >>functions should probably be classmethods
> >>
> >>ndarray.frombuffer
> >>ndarray.fromf
El dv 02 de 02 del 2007 a les 19:11 +0100, en/na Francesc Altet va
escriure:
> El dv 02 de 02 del 2007 a les 10:22 -0700, en/na Travis Oliphant va
> escriure:
> > Francesc Altet wrote:
> >
> > >Hi,
> > >
> > >We have been bitten by a small glitch related with the representation of
> > >native byt
El dv 02 de 02 del 2007 a les 10:22 -0700, en/na Travis Oliphant va
escriure:
> Francesc Altet wrote:
>
> >Hi,
> >
> >We have been bitten by a small glitch related with the representation of
> >native byteorders. Here is an example exposing the problem:
> >
> >
> >
> numpy.dtype('
Francesc Altet wrote:
>Hi,
>
>We have been bitten by a small glitch related with the representation of
>native byteorders. Here is an example exposing the problem:
>
>
>
numpy.dtype('>>>
>'='
>
>
numpy.dtype('>i4').newbyteorder('little').byteorder
>'<'
>
I think arange for complex numbers should work like meshgrid,
with the real and imaginary axis replacing the x and y axis. That would
mean something like this:
def complex_arange(start,end,stride):
def iscomplex(x):
if ((type(x)==complex) or (type(x)==complex64)
or (type(x)==co
On 2/2/07, Bruce Southey <[EMAIL PROTECTED]> wrote:
> I am curious why I do not see any mention of the compilers and
> versions that were used in this thread. Having just finally managed to
> get SciPY installed from scratch (but not with atlas), I could see
> that using different compliers or ver
Hi,
I am curious why I do not see any mention of the compilers and
versions that were used in this thread. Having just finally managed to
get SciPY installed from scratch (but not with atlas), I could see
that using different compliers or versions or options especially
compiling done at different
Hi,
We have been bitten by a small glitch related with the representation of
native byteorders. Here is an example exposing the problem:
>>> numpy.dtype('i4').newbyteorder('little').byteorder
'<'
[the example was run on a little endian machine]
We thought that native byteorder were represented
Travis Oliphant wrote:
> Sebastian Haase wrote:
>
>> Travis,
>> Could you explain what a possible downside of this would be !?
>
> I can't think of any downsides. I have to understand how class-methods
> are actually implemented, though before I could comment on speed
> implications of class m
On Thu, Feb 01, 2007 at 01:33:23PM -0600, Louis Wicker wrote:
> Dear list:
Hi,
may I suggest you to read this?
http://orange.blender.org/blog/stupid-memory-problems
It worth a read.
David
>
> I cannot seem to figure how to create arrays > 2 GB on a Mac Pro
> (using Intel chip and Tiger, 4.
On 2/1/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Christopher Barker wrote:
> > Sebastian Haase wrote:
> >
> >> Could you explain what a possible downside of this would be !?
> >> It seems that if you don't need to refer to a specific "self" object
> >> that a class-method is what it should - is
14 matches
Mail list logo
