Re: [matplotlib-devel] debugging python code

[Todd M. <jm...@st...>]

On Tue, 2004-12-07 at 10:52 +0800, Steve Chaplin wrote:
> On Mon, 2004-12-06 at 15:34 -0500, Perry Greenfield wrote:
> > I really appreciate Andrew's diagnosing the original problem and  
> > particularly in recognizing it as possibility here. This is a nasty  
> > kind of bug to figure out.
> The original bug was reported to numarray developers via the SourceForge
> bug tracking system back in February, the glibc patch was also applied
> in February. From Numarray 1.0 onwards a 'Special Note' has been
> included in the file numarray/Doc/Install.txt referencing the problem.
> 
> I believe the SourceForge bug report was the one
> 870660  Numarray: CFLAGS build problem  
> yet for some reason I can't locate it anymore. 

Here's the "numarray bugs tracker" link for this report:

http://sourceforge.net/tracker/index.php?func=detail&aid=870660&group_id=1369&atid=450446

My guess is that you were looking in the "numpy bugs tracker" where the
bug was originally filed but which is supposed to be for Numeric:

http://sourceforge.net/tracker/?group_id=1369&atid=101369

Numarray bugs which are filed in the numpy bugs tracker are moved to the
numarray bugs tracker.  They're both on the same SF project,  but the
numarray tracker is more hidden.  I'm sorry this is confusing.

Regards,
Todd