|
From: John H. <jd...@gm...> - 2009-05-21 02:57:10
|
On Wed, May 20, 2009 at 9:36 PM, Joshua J. Kugler <jo...@ee...> wrote: > So, my code has been running without flaw for quite some time now, and > thanks to the help of some folks here a few months back, I'm learning > more about matplotlib. But today I hit a wall. > > Under matplotlib 0.91.2/Py2.5, I'm getting this graph: > http://joshuakugler.com/images/good_graph.png >.. .snip > No, I haven't assembled a minimal test case (this is quite a complex > system, I spent several hours on this thinking I had broken my code > until it occurred to me to run it on an old Py2.5/mpl 0.91.2 setup), > and no I haven't trolled the changelogs to see what change in behavior > I might have hit, but I was wondering if anyone any ideas of what I > need to be checking off the top of their heads. You are running a really old mpl -- the last 0.91 release was about 16 months ago. If you want resolution against the latest tree, you will need to post an updated script exhibiting the problem. > P.S. Oh, and there is also a nice traceback I'm getting on other graphs > that seems to be related to this glitch, but I'll wait until I have the > first glitch fixed as the second glitch may get fixed in the process. Ahh, this is a tantalizing morsel. If only we had the traceback, we might be able to help... JDH JDH |