matplotlib-devel Mailing List for matplotlib

Doing the commands:
------------------------------
from matplotlib.matlab import *
plot((1,2),(3,4))
figtext(0.5,0.5,"$\sqrt 2$")
savefig("tryout.eps")
------------------------------
diplays the sqrt sign shifted upwards against the regular text.
-- 
_________________________________________Norbert Nemec
 Bernhardstr. 2 ... D-93053 Regensburg
 Tel: 0941 - 2009638 ... Mobil: 0179 - 7475199
 eMail: <No...@Ne...>

On Dec 7, 2004, at 2:07 AM, Andrew Straw wrote:
> On Dec 6, 2004, at 6:52 PM, 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
>
> Probably by the too-modest Steve Chaplin, I suspect. I forgot in my 
> previous email that a significant component of my late-phase debugging 
> consisted of emailing the numarray list, and getting an email from 
> Steven Chaplin, who had independently diagnosed the problem. He had 
> already gone much further than I -- he's the one who submitted the bug 
> report and patch to the glibc itself:
Sorry about that. I should have also thanked Steve for doing the hard 
part.

Hello,
I can confirm that the numarray version of matplotlib
(http://matplotlib.sourceforge.net/) crashes for me without this
patch, and does not crash any more after I applied the patch.
My setup: libc6 version 2.3.2.ds1-18, a Pentium 4 processor (has SSE)
and the atlas3-sse2 library installed.
references:
1) a test program and the patch is at
 http://sources.redhat.com/bugzilla/show_bug.cgi?id=3D10
2) the problem in the context of numarray is described at
 http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D870660&gro=
up_id=3D1369&atid=3D450446
I hope this helps,
Jochen
--=20
http://seehuhn.de/

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

On Dec 6, 2004, at 6:52 PM, 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
Probably by the too-modest Steve Chaplin, I suspect. I forgot in my 
previous email that a significant component of my late-phase debugging 
consisted of emailing the numarray list, and getting an email from 
Steven Chaplin, who had independently diagnosed the problem. He had 
already gone much further than I -- he's the one who submitted the bug 
report and patch to the glibc itself:
> This is the glibc bug report
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=10
Jochen, that bug report contains a C program which replicates the bug. 
Perhaps you could send that test program to the Debian bug tracking 
system to spur patching? (There is an additional comment on the glibc 
bugzilla page saying "The test program isn't really testing what it is 
supposed to (the SSE status is never touched) but the SSE control 
change is indeed wrong." You may want to address this first if you're 
up for this kind of low-level fun.)
To summarize, we owe a big thanks to Steve Chaplin. A heartfelt 
thanks, Steve!
Cheers!
Andrew

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. Perhaps thats one of the
reasons that the problem keeps getting rediscovered.
This is the glibc bug report
http://sources.redhat.com/bugzilla/show_bug.cgi?id=10
Steve