Re: [matplotlib-devel] segfault on specgram in svn

2006-12-08 Thread Glen W. Mabey
On Fri, Dec 08, 2006 at 01:54:56PM -0600, Glen W. Mabey wrote: > On Fri, Dec 08, 2006 at 01:44:03PM -0600, John Hunter wrote: > > > "Glen" == Glen W Mabey <[EMAIL PROTECTED]> writes: > > > > Glen> Hello, I've just switched to Python 2.5 and at the same time > > Glen> upgraded to numpy

Re: [matplotlib-devel] segfault on specgram in svn

2006-12-08 Thread Glen W. Mabey
On Fri, Dec 08, 2006 at 01:44:03PM -0600, John Hunter wrote: > > "Glen" == Glen W Mabey <[EMAIL PROTECTED]> writes: > > Glen> Hello, I've just switched to Python 2.5 and at the same time > Glen> upgraded to numpy 1.0.1 with today's svn matplotlib, using > Glen> the QtAgg backend (P

Re: [matplotlib-devel] segfault on specgram in svn

2006-12-08 Thread John Hunter
> "Glen" == Glen W Mabey <[EMAIL PROTECTED]> writes: Glen> Hello, I've just switched to Python 2.5 and at the same time Glen> upgraded to numpy 1.0.1 with today's svn matplotlib, using Glen> the QtAgg backend (PyQt3 3.17). This is on an AMD64 Glen> (Opteron) machine. Glen

[matplotlib-devel] segfault on specgram in svn

2006-12-08 Thread Glen W. Mabey
Hello, I've just switched to Python 2.5 and at the same time upgraded to numpy 1.0.1 with today's svn matplotlib, using the QtAgg backend (PyQt3 3.17). This is on an AMD64 (Opteron) machine. I get a segfault after these operations: In [1]:import numpy as N In [2]:specgram( N.random.randn( 256*50