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

On Thu, Jan 28, 2010 at 3:11 PM, 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] Removing datetime support for 1.4.x series ?

On Fri, Feb 5, 2010 at 3:09 AM, Charles R Harris wrote: > > I put 1.4.1 4-6 wks out to give the apprentice release guys some time. > > Thanks, a few weeks would be useful. I have been able to build an OS X installer, and am now trying to get Wine into shape. Patrick told me he set up a build env o

Re: [Numpy-discussion] Audio signal capture and processing

Gerardo Gutierrez wrote: > Hello. > > I'm working with audio signals with wavelet analisys, and I want to know > if someone has work with some audio capture (with the mic and through a > file) library so that I can get the time-series... I think the easiest for now is to record things in a file

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Fri, Feb 5, 2010 at 5:15 AM, Pauli Virtanen wrote: > to, 2010-02-04 kello 12:09 -0700, Charles R Harris kirjoitti: >> Realistically, I don't think Py3k will be ready by April-May. Fall is >> probably doable and maybe there will be some things for a SOC person >> to work on this summer. > > Well

Re: [Numpy-discussion] Efficiently converting numpy record array to a list of dictionary

Warren, thanks for the information. Vishal Charles de Gaulle - "The better I get to know men, the more I find myself loving dogs." On Thu, Feb 4, 2010 at 4:10

Re: [Numpy-discussion] Efficiently converting numpy record array to a list of dictionary

Thanks Robert :) Vishal Rana Samuel Goldwyn - "I don't think anyone should write their autobiography until after they're dead." On Thu, Feb 4, 2010 at 4:04 PM, Robert Kern wrote: > On Thu, Feb 4, 2010 at 16:26, Vishal Rana wrote:

Re: [Numpy-discussion] Efficiently converting numpy record array to a list of dictionary

Vishal, Robert's code does the trick, but--in case you are new to numpy record arrays-I thought I'd point out that the array itself already acts like a list of dictionaries: In [6]: import numpy as np In [7]: dt = np.dtype([('name', 'S30'),('age',int),('weight',float)]) In [8]: r = np.array([

Re: [Numpy-discussion] Efficiently converting numpy record array to a list of dictionary

On Thu, Feb 4, 2010 at 16:26, Vishal Rana wrote: > How do I convert the numpy record array below: > recs = [('Bill', 31, 260.0), ('Fred', 15, 145.0)] > r = rec.fromrecords(recs, names='name, age, weight', formats='S30, i2, f4') > to a list of dictionary like: > [{'name': 'Bill', 'age': 31, 'weight

Re: [Numpy-discussion] Efficiently converting numpy record array to a list of dictionary

On Thu, Feb 4, 2010 at 3:46 PM, Keith Goodman wrote: > On Thu, Feb 4, 2010 at 2:26 PM, Vishal Rana wrote: >> How do I convert the numpy record array below: >> recs = [('Bill', 31, 260.0), ('Fred', 15, 145.0)] >> r = rec.fromrecords(recs, names='name, age, weight', formats='S30, i2, f4') >> to a l

Re: [Numpy-discussion] Efficiently converting numpy record array to a list of dictionary

On Thu, Feb 4, 2010 at 2:26 PM, Vishal Rana wrote: > How do I convert the numpy record array below: > recs = [('Bill', 31, 260.0), ('Fred', 15, 145.0)] > r = rec.fromrecords(recs, names='name, age, weight', formats='S30, i2, f4') > to a list of dictionary like: > [{'name': 'Bill', 'age': 31, 'weig

Re: [Numpy-discussion] Unexpected tofile() behavior

On Feb 4, 2010, at 4:02 PM, Christopher Barker wrote: > Jeffery Kline wrote: >> Am I doing something stupid or overlooking something obvious? >> >> My system is Mac os x 10.6.2, running python 2.6.4. > > Mac OS is case=preserving, but not case dependent with file names, I > think the OS is wr

[Numpy-discussion] Efficiently converting numpy record array to a list of dictionary

How do I convert the numpy record array below: recs = [('Bill', 31, 260.0), ('Fred', 15, 145.0)] r = rec.fromrecords(recs, names='name, age, weight', formats='S30, i2, f4') to a list of dictionary like: [{'name': 'Bill', 'age': 31, 'weight': 260.0}, 'name': 'Fred', 'age': 15, 'weight': 145.0}] _

Re: [Numpy-discussion] Unexpected tofile() behavior

Jeffery Kline wrote: > Am I doing something stupid or overlooking something obvious? > > My system is Mac os x 10.6.2, running python 2.6.4. Mac OS is case=preserving, but not case dependent with file names, I think the OS is writing over your file. -Chris -- Christopher Barker, Ph.D. Ocea

Re: [Numpy-discussion] Unexpected tofile() behavior

to, 2010-02-04 kello 15:28 -0600, Jeffery Kline kirjoitti: > I am experiencing unexpected behavior with the tofile() function. I > try to write two files with but distinct names, but only one of the > files is written. > > The following code illustrates. For me, it only writes the file 't.bin'. >

Re: [Numpy-discussion] Unexpected tofile() behavior

On Thu, Feb 4, 2010 at 1:28 PM, Jeffery Kline wrote: > I am experiencing unexpected behavior with the tofile() function.  I try to > write two files with but distinct names, but only one of the files is written. > > The following code illustrates. For me, it only writes the file 't.bin'. > > from

[Numpy-discussion] Unexpected tofile() behavior

I am experiencing unexpected behavior with the tofile() function. I try to write two files with but distinct names, but only one of the files is written. The following code illustrates. For me, it only writes the file 't.bin'. from numpy import * t=arange(0,1,0.1) T=arange(0,1,0.1) t.tofile('t.

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 1:15 PM, Pauli Virtanen wrote: > to, 2010-02-04 kello 12:09 -0700, Charles R Harris kirjoitti: > > Realistically, I don't think Py3k will be ready by April-May. Fall is > > probably doable and maybe there will be some things for a SOC person > > to work on this summer. > >

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

to, 2010-02-04 kello 12:09 -0700, Charles R Harris kirjoitti: > Realistically, I don't think Py3k will be ready by April-May. Fall is > probably doable and maybe there will be some things for a SOC person > to work on this summer. Well, we have many components of Py3 support in place in the SVN tr

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

I'd like to say that I am +1 with everything that has been said against breakage. On top of that, I'd like to echo the conversation I had with Fabian Pedregosa, who works in my group full time on scikit learn. Fabian was doing binaries. I asked him what numpy version he had used to build to the

Re: [Numpy-discussion] Audio signal capture and processing

On 4-Feb-10, at 2:18 PM, Gerardo Gutierrez wrote: > I'm working with audio signals with wavelet analisys, and I want to > know if > someone has work with some audio capture (with the mic and through a > file) > library so that I can get the time-series... > Also I need to play the transformed

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 2:37 AM, Travis Oliphant wrote: > Perhaps one way to articulate my perspective is the following: > There are currently 2 groups of NumPy users: >  1)  those who have re-compiled all of their code for 1.4.0 >  2)  those who haven't It may be useful to keep in mind one import

[Numpy-discussion] Audio signal capture and processing

Hello. I'm working with audio signals with wavelet analisys, and I want to know if someone has work with some audio capture (with the mic and through a file) library so that I can get the time-series... Also I need to play the transformed signal. Thanks. * *"Solo existen 10 tipos de personas en e

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 11:22 AM, Jarrod Millman wrote: > On Thu, Feb 4, 2010 at 10:06 AM, Charles R Harris > wrote: > > Let me propose a schedule: > > > > 1.4.1 : Bug fix, no datetime, ~4-6wks from now. > > 2.0 : API break, datetime, hasobject changes, April - May timeframe > > 2.1 : Python 3K -

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 10:06 AM, Charles R Harris wrote: > Let me propose a schedule: > > 1.4.1 : Bug fix, no datetime, ~4-6wks from now. > 2.0 : API break, datetime, hasobject changes, April - May timeframe > 2.1 : Python 3K - Fall I like your schedule in general. The only change I would sugges

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

David Cournapeau wrote: >>> 1.4.x, not about removing datetime altogether. It seems that datetime in >>> 1.4.x has few users, >> Of course it has few users -- it's brand new! > > Yes, but that's my point: removing it has low impact, whereas breaking > ABI has a big impact. My point is that it wil

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 10:38 AM, Matthew Brett wrote: > Hi, > > > I think Group 1 is a negligible epsilon of Group 2, and moreover, > > Group 1 is the most likely to be able to deal with those issues. > > It is time for an on list vote? > > I must say, although I know it is not straightforward, th

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

Hi, > I think Group 1 is a negligible epsilon of Group 2, and moreover, > Group 1 is the most likely to be able to deal with those issues. It is time for an on list vote? I must say, although I know it is not straightforward, that I agree with David that, we should act in favor of our new and le

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 4:37 PM, Travis Oliphant wrote: > > On Feb 4, 2010, at 12:59 AM, Charles R Harris wrote: > > > On Wed, Feb 3, 2010 at 11:48 PM, Travis Oliphant > wrote: >> >> On Feb 2, 2010, at 11:59 PM, David Cournapeau wrote: >> >> Travis Oliphant wrote: >> >> On Feb 2, 2010, at 11:46 PM

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 3:46 PM, Travis Oliphant wrote: > If the issue is having too many releases that are .X releases, then let's > just slow that down. The issue is not so much version numbering - I think keeping compatibility between .X releases is slightly better because that's the usually f

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

to, 2010-02-04 kello 07:42 -0500, Darren Dale kirjoitti: [clip] > and it could/should be released as numpy-2.0. Then when when numpy for > py-3.0 is ready, which will presumably require ABI breakage, it could > be called numpy-3.0. The Py3 transition will most likely be invisible to Py2 users, and

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 3:21 AM, Francesc Alted wrote: > A Thursday 04 February 2010 08:46:01 Charles R Harris escrigué: >> > Perhaps one way to articulate my perspective is the following: >> > >> > There are currently 2 groups of NumPy users: >> > >> >  1)  those who have re-compiled all of their

[Numpy-discussion] Scalar-ndarray arguments passed to not_equal

Hi, I'm just coding a package for uncertain arrays using the accelerated numpy functionality intensively. I'm sorry, but I have to give some background information first. The package provides a class upy.undarray, which holds the nominal value and the uncertainty information. It has methods __a

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

A Thursday 04 February 2010 08:46:01 Charles R Harris escrigué: > > Perhaps one way to articulate my perspective is the following: > > > > There are currently 2 groups of NumPy users: > > > > 1) those who have re-compiled all of their code for 1.4.0 > > 2) those who haven't > > I think David h