Re: [Numpy-discussion] Warning on http://scipy.org/ about binary incompatibility ?

Charles R Harris wrote: > > > On Thu, Jan 28, 2010 at 12:33 AM, David Cournapeau > mailto:da...@silveregg.co.jp>> wrote: > > Because Travis was against it when it was suggested last september or > so. And removing in 1.4.x a feature introduced in 1.4.0 is weird. > > > But wasn't that

Re: [Numpy-discussion] Warning on http://scipy.org/ about binary incompatibility ?

On Thu, Jan 28, 2010 at 12:33 AM, David Cournapeau wrote: > Charles R Harris wrote: > > > > > > On Wed, Jan 27, 2010 at 11:39 PM, David Cournapeau > > mailto:da...@silveregg.co.jp>> wrote: > > > > Charles R Harris wrote: > > > > > > > > > On Wed, Jan 27, 2010 at 6:20 PM, David C

Re: [Numpy-discussion] dtype and logical_and

On Thu, Jan 28, 2010 at 8:39 AM, Robert Kern wrote: > On Thu, Jan 28, 2010 at 10:31, Keith Goodman wrote: >> I noticed that & (logical and) does support float dtype: > > & is not logical_and(). It is bitwise_and(). That explains it. Thank you. ___ NumP

Re: [Numpy-discussion] dtype and logical_and

On Thu, Jan 28, 2010 at 10:31, Keith Goodman wrote: > I noticed that & (logical and) does support float dtype: & is not logical_and(). It is bitwise_and(). -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt t

[Numpy-discussion] dtype and logical_and

I noticed that & (logical and) does support float dtype: >> b = np.array([True, False]) >> f = np.array([1.0, 2.0]) >> i = np.array([1, 2]) >> b & b array([ True, False], dtype=bool) >> i & i array([1, 2]) >> i & f TypeError: unsupported operand type(s) for &: 'int' and 'float' But this wo

Re: [Numpy-discussion] NumPy-Discussion Digest, Vol 40, Issue 70

is. This is thus a flaw in the > general design/implementation of the savefig function, but is there an > alternative function to enable me achieve what I need? Is there > perhaps a possible tweak to savefig to make it do the same? > > Thanks in advance, > > Robert

Re: [Numpy-discussion] Warning on http://scipy.org/ about binary incompatibility ?

On Thu, Jan 28, 2010 at 9:09 AM, Dag Sverre Seljebotn wrote: > josef.p...@gmail.com wrote: >> On Thu, Jan 28, 2010 at 1:39 AM, David Cournapeau >> wrote: >> >>> Charles R Harris wrote: >>> On Wed, Jan 27, 2010 at 6:20 PM, David Cournapeau >>> > wrote:

Re: [Numpy-discussion] [ANN] New open source project for labeled arrays

On Thu, Jan 28, 2010 at 6:53 AM, Bruce Southey wrote: > On Wed, Jan 27, 2010 at 9:24 PM, Keith Goodman wrote: >> On Wed, Jan 27, 2010 at 7:13 PM, Pierre GM wrote: >>> On Jan 27, 2010, at 9:10 PM, Keith Goodman wrote: I recently opened sourced one of my packages. It is a labeled array t

Re: [Numpy-discussion] [ANN] New open source project for labeled arrays

On Wed, Jan 27, 2010 at 9:24 PM, Keith Goodman wrote: > On Wed, Jan 27, 2010 at 7:13 PM, Pierre GM wrote: >> On Jan 27, 2010, at 9:10 PM, Keith Goodman wrote: >>> I recently opened sourced one of my packages. It is a labeled array >>> that I call larry. >>> >>> A two-dimensional larry, for exampl

Re: [Numpy-discussion] wired error message in scipy.sparse.eigen function: Segmentation fault

On Thu, Jan 28, 2010 at 12:11 AM, David Cournapeau wrote: > Jankins wrote: >> Yes. I am using scipy.sparse.linalg.eigen.arpack. >> >> The exact output is: >> >> /usr/local/lib/python2.6/dist-packages/scipy/sparse/linalg/eigen/arpack/_arpack.so > > I need the output of ldd on this file, actually, i

Re: [Numpy-discussion] Warning on http://scipy.org/ about binary incompatibility ?

josef.p...@gmail.com wrote: > On Thu, Jan 28, 2010 at 1:39 AM, David Cournapeau > wrote: > >> Charles R Harris wrote: >> >>> On Wed, Jan 27, 2010 at 6:20 PM, David Cournapeau >> > wrote: >>> >>> josef.p...@gmail.com wrote: >>

Re: [Numpy-discussion] Warning on http://scipy.org/ about binary incompatibility ?

On Thu, Jan 28, 2010 at 1:39 AM, David Cournapeau wrote: > Charles R Harris wrote: >> >> >> On Wed, Jan 27, 2010 at 6:20 PM, David Cournapeau > > wrote: >> >>     josef.p...@gmail.com wrote: >>      > Can we/someone add a warning on the f

Re: [Numpy-discussion] is there any alternative to savefig?

Robert Kiwanuka wrote: > Hi all, > > I wonder if anyone knows any alternative function in pylab (or > otherwise) that could be used to save an image. My problem is as > follows: > > --- > from pylab import * > ... > > figure(1) > fig1 = gca() > figure(2) > fig2 = gca() > figure(3) > fig

Re: [Numpy-discussion] is there any alternative to savefig?

to, 2010-01-28 kello 12:50 +, Robert Kiwanuka kirjoitti: [clip] > If I could do something like fig1.savefig("y1-x1.png") or savefig("y1- > x1.png").fig1, this would solve the problem but I'm not aware of any > such methods or modules to enable this. This is thus a flaw in the > general design/

[Numpy-discussion] is there any alternative to savefig?

Hi all, I wonder if anyone knows any alternative function in pylab (or otherwise) that could be used to save an image. My problem is as follows: --- from pylab import * ... figure(1) fig1 = gca() figure(2) fig2 = gca() figure(3) fig3 = gca() for i,data_file in enumerate(data_file_li