matplotlib-users Mailing List for matplotlib

In article <450...@no...>,
 Christopher Barker <Chr...@no...> wrote:
> Russell E Owen wrote:
> > Interesting idea. I'm not sure I'd know how to use more than one numerix 
> > option at once,
> 
> well, I dint' mean more than one numerix option, exactly. What I meant 
> was that MPL is using numarray, but another module you've imported is 
> using Numeric (or numpy or whatever).
Ah. I can guarantee that's happening. Some of my code uses Numeric (due 
to high speed on short arrays) and some uses numarray (because I started 
using it for all new code when it looked like it would take over). I 
hope to switch to numpy for everything once the dust settles, but I 
don't want to force my users to all move at once (a lot of them are on 
unix and will have to manually install numpy -- no big deal, but I get 
complaints every time I require a new package).
> ...Does it happen with wxAgg? or just plain ol Agg? also try the non-agg TK 
> back-end.
I don't have wx or gtk installed, so no easy way to test those backends.
It does not crash with plain old Agg (but of course I don't see any 
plot).
I'll be happy to try the "non-agg TK back-end" if you can tell me what 
setting to use for it. I didn't see it in the matplotlibrc's list of 
options (but WXAgg is also missing from that particular list), nor on 
the "Which backend should I use?" page.
> If not, then you've apparently found a tkAgg bug.
> 
> TK has always been a bit of a second-class citizen on the Mac -- why 
> haven't you switched to wx yet? ;-)
I started this project several years ago and at the time Tcl/Tk was the 
only game in town for Mac+unix+windows cross-platform support. 
Admittedly the Mac support was poor, but it has gotten much better, and 
I like Tkinter pretty well overall. It would be a major job to switch 
now and I doubt I can justify the expense and time. Sometimes I wish I'd 
used Java, even though the I strongly prefer Python, just to get a 
standard GUI.
I'm bulding matplotlib from source now, just to see if there might be 
some quirk about the installer package.
-- Russell

At 3:12 PM -0700 9/15/06, Christopher Barker wrote:
>Russell E Owen wrote:
>>Interesting idea. I'm not sure I'd know how to use more than one 
>>numerix option at once,
>
>well, I dint' mean more than one numerix option, exactly. What I 
>meant was that MPL is using numarray, but another module you've 
>imported is using Numeric (or numpy or whatever).
Ah. I can guarantee that's happening. Some of my code uses Numeric 
(due to high speed on short arrays) and some uses numarray (because I 
started using it for all new code when it looked like it would take 
over). I hope to switch to numpy for everything once the dust 
settles, but I don't want to force my users to all move at once (a 
lot of them are on unix and will have to manually install numpy -- no 
big deal, but I get complaints every time I require a new package).
> > but it did inspire me to try a few things:
>
>>backend : TkAgg
>>numerix : numarray
>>interactive : True
>>and the crash still happens:
>>from pylab import *
>>plot([1,2,3,4])
>
>>I also tried setting numerix to Numeric and it still happens.
>
>Does it happen with wxAgg? or just plain ol Agg? also try the 
>non-agg TK back-end.
I don't have wx or gtk installed, so no easy way to test those backends.
It does not crash with plain old Agg (but of course I don't see any plot).
I'll be happy to try the "non-agg TK back-end" if you can tell me 
what setting to use for it. I didn't see it in the matplotlibrc's 
list of options (but WXAgg is also missing from that particular 
list), nor on the "Which backend should I use?" page.
>If not, then you've apparently found a tkAgg bug.
>
>TK has always been a bit of a second-class citizen on the Mac -- why 
>haven't you switched to wx yet? ;-)
I started this project several years ago and at the time Tcl/Tk was 
the only game in town for Mac+unix+windows cross-platform support. 
Admittedly the Mac support was poor, but it has gotten much better, 
and I like Tkinter pretty well overall. It would be a major job to 
switch now and I doubt I can justify the expense and time. Sometimes 
I wish I'd used Java, even though the I strongly prefer Python, just 
to get a standard GUI.
I'll try bulding matplotlib from source, just to see if there might 
be some quirk about the installer package.
-- Russell

Russell E Owen wrote:
> Interesting idea. I'm not sure I'd know how to use more than one numerix 
> option at once,
well, I dint' mean more than one numerix option, exactly. What I meant 
was that MPL is using numarray, but another module you've imported is 
using Numeric (or numpy or whatever).
 > but it did inspire me to try a few things:
> backend : TkAgg
> numerix : numarray
> interactive : True
> and the crash still happens:
> from pylab import *
> plot([1,2,3,4])
> I also tried setting numerix to Numeric and it still happens.
Does it happen with wxAgg? or just plain ol Agg? also try the non-agg TK 
back-end.
If not, then you've apparently found a tkAgg bug.
TK has always been a bit of a second-class citizen on the Mac -- why 
haven't you switched to wx yet? ;-)
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

In article <row...@se...>,
 "Russell E. Owen" <ro...@ce...> 
 wrote:
> I'm trying to figure out a matplotlib crash on MacOS X.
> 
> When I try to plot anything the program exits with:
> alloc: invalid block: 0xa08acb4: a 74 0
...
some followup info:
- This is with matplotlib 0.87.5, but also seen with 0.87.4 and 0.87.2
- This is with ActiveState Tcl/Tk 8.4.11, not 8.4.13 as I originally said
I tried the test again with "debug-annoying" level logging. Before 
running it I:
- deleted everything in ~/.matplotlibrc.
- .../site-packages/matplotlib/mpl-data to ~/.matplotlibrc and stripped 
out all but a few options (something I'd never tried before, but I'm 
hoping it'll leave me a matplotlibrc file that is compatible with future 
versions of matplotlib, for a change):
backend : TkAgg
numerix : numarray 
interactive : False
verbose.level : debug-annoying
verbose.fileo : sys.stdout
I then ran the test:
>>> from pylab import *
>>> plot([1,2,3,4])
>>> show()
The crash happens after the show():
...
RendererAgg.draw_text
RendererAgg._get_agg_font
alloc: invalid block: 0xa08acb4: a 74 0
The full log is here:
<http://rowen.astro.washington.edu/mpl.txt>
One other thing that may be relevant (and is in the log): whenever I run 
matplotlib for the first time after deleting the font cache, I always 
get a spate of warnings like this:
455: UserWarning: Could not open font file 
/System/Library/Fonts/LastResort.dfont
-- Russell

I'm trying to figure out a matplotlib crash on MacOS X.
When I try to plot anything the program exits with:
alloc: invalid block: 0xa08acb4: a 74 0
I first saw this with a program that uses the object interface, but then 
I tried the simplest pylab demo I could find and the same thing happened.
Setup:
- matplotlib installed from the universal package at pythonmac.org
 configured to use numarray (1.5.1) and the TkAgg back end
- MacOS X 10.4.3 on a PPC mac
- ActiveState Aqua Tcl/Tk 8.4.13
- seen with two different versions of python:
 - ActiveState python 2.4.3 (PPC-only)
 - universal Python 2.4.3 (with _tkinter.so modified to find my Tcl/Tk)
Any ideas?
-- Russell

Attached is an example. It seems like it autosizes to the initial 
data and from then on only uses that for autoscale purposes. I only 
noticed that while making this test app because I let it autoscale 
the x axis in this one.
R.

>>>>> "Richard" == Richard Harvey Chapman <hch...@3g...> writes:
 Richard> I'm using the latest matplotlib with wxPython 2.6.2.1 and
 Richard> the WxAGG backend. I have plotted a figure with 5
 Richard> subplots. I intentionally only plotted the first 10
 Richard> points of all of my data traces so I can simulate the
 Richard> look of real-time data. That is, I keep my xlim set to
 Richard> (now-60, now) for a window showing the last 60 seconds
 Richard> only. For the y-axis, I'd like it to autoscale, but it
 Richard> never does. I've tried calling
 Richard> axes.autoscale_view(scalex=False, scaley=True) for each
 Richard> subplot, but with no effect. For each update, I take each
 Richard> line in each subplot and update the x and y data with
 Richard> set_data(). I just add a few points every few seconds. Am
 Richard> I missing something? Why can't I get the y autoscaling to
 Richard> work? Autoscaling is on by default, and I've called
 Richard> get_autoscale_on() to confirm it.
Are you calling fig.canvas.draw() after the autoscale?
If you are still having troubles, please post a complete example....
JDH

I'm using the latest matplotlib with wxPython 2.6.2.1 and the WxAGG 
backend. I have plotted a figure with 5 subplots. I intentionally 
only plotted the first 10 points of all of my data traces so I can 
simulate the look of real-time data. That is, I keep my xlim set to 
(now-60, now) for a window showing the last 60 seconds only. For the 
y-axis, I'd like it to autoscale, but it never does. I've tried 
calling axes.autoscale_view(scalex=False, scaley=True) for each 
subplot, but with no effect. For each update, I take each line in 
each subplot and update the x and y data with set_data(). I just add 
a few points every few seconds. Am I missing something? Why can't I 
get the y autoscaling to work? Autoscaling is on by default, and I've 
called get_autoscale_on() to confirm it.
Thank you,
Harvey
R.

VGhhbmtzLA0KSSBhY3R1YWxseSBnb3QgYSB3b3JrIGFyb3VuZCBub3cuIFRoYW5rcyBmb3IgdGhl
IGZvbGxvdy4NCg0KQ2hyaXMgQnJpbmxleSAoY2hyaXMuYnJpbmxleUBvcmJpdHouY29tKQ0KT3Ji
aXR6IC0gQUEuY29tIE9wZXJhdGlvbnMgDQpQaG9uZTogMzEyLTg5NC00Nzg3DQpDZWxsOiAzMTIt
NDc5LTgxOTMNClBhZ2VyOiA4NjYtMjkyLTM1MDggDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBKb2huIEh1bnRlcg0KVG86IEJyaW5sZXksIENocmlzDQpDQzogbWF0cGxvdGxp
Yi11c2Vyc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNClNlbnQ6IEZyaSBTZXAgMTUgMTE6Mjk6MDcg
MjAwNg0KU3ViamVjdDogUmU6IFtNYXRwbG90bGliLXVzZXJzXSBwbG90X2RhdGUgKyB4ZGF0YSAm
IHlkYXRhIG11c3QgYmUgc2FtZSBsZW4NCg0KPj4+Pj4gIkJyaW5sZXksIiA9PSBCcmlubGV5LCBD
aHJpcyA8Q2hyaXMuQnJpbmxleUBvcmJpdHouY29tPiB3cml0ZXM6DQoNCiAgICBDaHJpcz4gSGks
IEkgYW0gaGF2aW5nIHRyb3VibGUgZ2V0dGluZyBhIHZhcmlhdGlvbiBvZiB0aGUNCiAgICBDaHJp
cz4gdHV0b3JpYWwgcGxvdF9kYXRlKCkgdG8gd29yay4gSSBnZXQgdGhlIGNsYXNzaWM6DQogICAg
Q2hyaXM+IFJ1bnRpbWVFcnJvcjogeGRhdGEgYW5kIHlkYXRhIG11c3QgYmUgdGhlIHNhbWUgbGVu
Z3RoLg0KDQpIbW0sIGRpZG4ndCBrbm93IHRoaXMgaGFkIGFjaGlldmVkIGNsYXNzaWMgc3RhdHVz
Li4uLg0KDQogICAgQ2hyaXM+IFRoZSB0dXRvcmlhbCBvbiB0aGUgbWF0cGxvdGxpYiBzaXRlIHNo
b3dzIGhvdyB0byBwbG90DQogICAgQ2hyaXM+IGRhdGVzIHVzaW5nIHdob2xlIGRheXMuIEkgYW0g
cGxvdHRpbmcgdXNpbmcgbXVsdGlwbGUNCiAgICBDaHJpcz4gZGF5cyBzaG93aW5nIGVhY2ggbWlu
dXRlIG9mIHRoZSBkYXkuDQoNCiAgICBDaHJpcz4gQmVmb3JlIEkgcnVuIHBsb3RfZGF0ZSBJIHNl
dHVwIHRvIGRhdGV0aW1lIHZhcnMgYW5kDQogICAgQ2hyaXM+IHN1YnRyYWN0IHRoZW0gdG8gZ2V0
IHRoZSB0aW1lZGVsdGEgc28uLiB0aW1lZGVsdGEgPQ0KICAgIENocmlzPiBlbmRkYXRlIC0gc3Rh
cnRkYXRlLg0KDQogICAgQ2hyaXM+IEkgdGhlbiB1c2UgZHJhbmdlKHN0YXJ0ZGF0ZSwgZW5kZGF0
ZSwgdGltZWRlbHRhKQ0KDQpUaGlzIGRvZXNuJ3QgbG9vayByaWdodCwgc2luY2UgeW91ciBkZWx0
YSBlcXVhbHMgdGhlIGVudGlyZSByYW5nZS4NClVzdWFsbHkgeW91IHdhbnQgeW91ciBkZWx0YSB0
byBiZSBzbWFsbGVyLg0KDQogICAgQ2hyaXM+IEkgcGFzcyB0aGlzIHJhbmdlIGludG8gdGhlIHBs
b3RfZGF0ZSBmdW5jdGlvbiB3aXRoIG15IHkNCiAgICBDaHJpcz4gYXhpcyBkYXRhLCB3aGljaCBJ
IGhhdmUgY29uZmlybWVkIGlzIG51bWVyaWMgYW5kIHRoZQ0KICAgIENocmlzPiBzYW1lIG51bWJl
ciBvZiBlbnRyaWVzIGFzIHRoZSBudW1iZXIgb2YgZGF0ZXRpbWVzIEkgd2FudA0KICAgIENocmlz
PiB0byBwbG90Lg0KDQpNYXliZSB5b3UgbWFkZSBhIG1pc3Rha2UgaGVyZT8gIEl0IHNvbWV0aW1l
cyBoYXBwZW5zIHdoZW4gd29ya2luZw0KaW50ZXJhY3RpdmVseSB0aGF0IHlvdSBhZGQgc29tZSBi
YWQgZGF0YSB0byBhIHBsb3QsIHJlYWxpemUgeW91cg0KbWlzdGFrZSwgdGhlbiBhZGQgZ29vZCBk
YXRhLCBidXQgc3RpbGwgc2VlIHRoZSBlcnJvci4gIFdoZW4gdGhpcw0KaGFwcGVucywgaXQgaXMg
dXN1YWxseSBiZWNhdXNlIHlvdXIgImhvbGQiIHN0YXRlIGlzIG9uIGFuZCB0aGUNCnByZXZpb3Vz
IGRhdGEgaXMgc3RpbGwgaW4geW91ciBwbG90LiAgWW91IGNhbiBjbGVhciB0aGUgZmlndXJlIHdp
dGgNCmZpZy5jbGYoKQ0KDQpJZiB5b3UgYXJlIHN0aWxsIGhhdmluZyBhIHByb2JsZW0sIHBvc3Qg
YSBjb21wbGV0ZSBleGFtcGxlIHRoYXQgd2UNCmNhbiBydW4uDQoNCiAgICBDaHJpcz4gQ2xlYXJs
eSBJIGFtIGluY29ycmVjdGx5IHRlbGxpbmcgcGxvdGxpYiB0aGUgaW50ZXJ2YWxzDQogICAgQ2hy
aXM+IG9mIHRpbWUgSSB3YW50IHRvIHBsb3QuIFdoYXQgaXMgdGhlIGJlc3Qgd2F5IHRvIHBsb3Qg
b3V0DQogICAgQ2hyaXM+IGFuIGludGVyZGF5IGNoYXJ0IHRoYXQgaGFzIHRpY2tzIGZvciBlYWNo
IG1pbj8NCg0KICBmcm9tIG1hdHBsb3RsaWIuZGF0ZXMgaW1wb3J0IE1pbnV0ZUxvY2F0b3INCiAg
Li4uDQoNCiAgIyBldmVyeSBtaW51dGUNCiAgYXgueGF4aXMuc2V0X21ham9yX2xvY2F0b3IoTWlu
dXRlTG9jYXRvcigpKSANCg0KICAjIG9yIGV2ZXJ5IDUgbWludXRlcw0KICBheC54YXhpcy5zZXRf
bWFqb3JfbG9jYXRvcihNaW51dGVMb2NhdG9yKG54LmFyYW5nZSgwLDYxLDUpKSkNCg0KWW91J2xs
IHByb2JhYmx5IGFsc28gd2FudCB0byBzZXQgdGhlIEZvcm1hdHRlciAtLSBzZWUgdGhlIHVzZXIn
cyBndWlkZQ0KY2hhcHRlciBvbiB0aWNrIGxvY2F0aW5nIGFuZCBmb3JtYXR0aW5nIGFuZCBhbHNv
DQoNCiAgaHR0cDovL21hdHBsb3RsaWIuc2YubmV0L21hdHBsb3RsaWIudGlja2VyLmh0bWwNCiAg
aHR0cDovL21hdHBsb3RsaWIuc2YubmV0L21hdHBsb3RsaWIuZGF0ZXMuaHRtbA0KDQphbmQgdGhl
c2UgZXhhbXBsZXMNCg0KICBtcGwvZXhhbXBsZXM+IGdyZXAgLWwgTG9jYXRvciAqLnB5DQogIGRh
c2h0aWNrLnB5DQogIGRhdGVfZGVtbzEucHkNCiAgZGF0ZV9kZW1vMi5weQ0KICBkYXRlX2RlbW9f
Y29udmVydC5weSANCiAgZGF0ZV9kZW1vX3JydWxlLnB5DQogIGZpbmFuY2VfZGVtby5weQ0KICBt
YWpvcl9taW5vcl9kZW1vMS5weQ0KICBtYWpvcl9taW5vcl9kZW1vMi5weQ0KICBzdG9ja19kZW1v
LnB5DQo=

>>>>> "Brinley," == Brinley, Chris <Chr...@or...> writes:
 Chris> Hi, I am having trouble getting a variation of the
 Chris> tutorial plot_date() to work. I get the classic:
 Chris> RuntimeError: xdata and ydata must be the same length.
Hmm, didn't know this had achieved classic status....
 Chris> The tutorial on the matplotlib site shows how to plot
 Chris> dates using whole days. I am plotting using multiple
 Chris> days showing each minute of the day.
 Chris> Before I run plot_date I setup to datetime vars and
 Chris> subtract them to get the timedelta so.. timedelta =
 Chris> enddate - startdate.
 Chris> I then use drange(startdate, enddate, timedelta)
This doesn't look right, since your delta equals the entire range.
Usually you want your delta to be smaller.
 Chris> I pass this range into the plot_date function with my y
 Chris> axis data, which I have confirmed is numeric and the
 Chris> same number of entries as the number of datetimes I want
 Chris> to plot.
Maybe you made a mistake here? It sometimes happens when working
interactively that you add some bad data to a plot, realize your
mistake, then add good data, but still see the error. When this
happens, it is usually because your "hold" state is on and the
previous data is still in your plot. You can clear the figure with
fig.clf()
If you are still having a problem, post a complete example that we
can run.
 Chris> Clearly I am incorrectly telling plotlib the intervals
 Chris> of time I want to plot. What is the best way to plot out
 Chris> an interday chart that has ticks for each min?
 from matplotlib.dates import MinuteLocator
 ...
 # every minute
 ax.xaxis.set_major_locator(MinuteLocator()) 
 # or every 5 minutes
 ax.xaxis.set_major_locator(MinuteLocator(nx.arange(0,61,5)))
You'll probably also want to set the Formatter -- see the user's guide
chapter on tick locating and formatting and also
 http://matplotlib.sf.net/matplotlib.ticker.html
 http://matplotlib.sf.net/matplotlib.dates.html
and these examples
 mpl/examples> grep -l Locator *.py
 dashtick.py
 date_demo1.py
 date_demo2.py
 date_demo_convert.py 
 date_demo_rrule.py
 finance_demo.py
 major_minor_demo1.py
 major_minor_demo2.py
 stock_demo.py

>>>>> "axel" == axel breuer <axe...@bn...> writes:
 axel> Hi, I run python + pylab in Linux.
 axel> When I type:
 >>>> import pylab pylab.plot([1,2,3])
 axel> A window pops up but nothing is drawn in it (!?!). So I
 axel> type:
 >>>> pylab.draw()
 axel> The plot is then correctly drawn ( but I still do not see
 axel> the lower buttons of the toolbar !?!)
 axel> My problem is that I cannot close the plot window nor by
 axel> clicking the "upper-right-cross" button of that wndow, nor
 axel> by typing:
 >>>> pylab.close()
 axel> The window remains displayed...
You must uses a threaded python shell to use GTK* in interactive mode,
as described at http://matplotlib.sf.net/interactive.html
Recommended is 
 > ipython -pylab
or 
 > ipython -gthread
JDH

>>>>> "Esdras" == Esdras Caleb <ach...@gm...> writes:
 Esdras> its this tipe of grafics I want see anexed img grafics of
 Esdras> experimental poits, tehrtea are a way to do it in
 Esdras> mathplot? 2006年9月12日, David Chin
x, y = nx.mlab.rand(2,1000)
plot(x, y, '+')
JDH

Okay, I appear to have my self in dependency hell now :s
I'm trying to get a working installation of numpy,scipy and mpl
together. I'm going about this using the scipy superpack download,
which contains all three and a few supporting things. Trouble is, the
build of mpl contained in the superpack is missing it's __init__.py
file - so python doesnt recognise it as a module to import.
It was suggested by the SciPy crowd that I should pinch the
__init__.py from a 'working' package of mpl and using that to make the
module work. Sounds a bit of a bodged way of doing this, and indeed,
using the __init__.py from the most recent mpl release produces the
following:
>>> from pylab import *
Traceback (most recent call last):
 File "<stdin>", line 1, in ?
 File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/pylab.py",
line 1, in ?
 from matplotlib.pylab import *
 File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/pylab.py",
line 200, in ?
 from axes import Axes, PolarAxes
 File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/axes.py",
line 15, in ?
 from axis import XAxis, YAxis
 File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/axis.py",
line 25, in ?
 from font_manager import FontProperties
 File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/font_manager.py",
line 39, in ?
 from matplotlib import ft2font
ImportError: Failure linking new module:
/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/ft2font.so:
Library not loaded: /usr/local/lib/libfreetype.6.dylib
 Referenced from:
/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/ft2font.so
 Reason: image not found
libfreetype issues.
Anyone got a solution to this problem that will get me a working
install of all 3 modules?
Cheers,
Dave
On 15/09/06, Charlie Moad <cw...@gm...> wrote:
> mpl 0.87.5 is compiled against numpy 1.0b5. It should remain
> compatible with future release of 1.0.
>
> On 9/15/06, David Andrews <irb...@gm...> wrote:
> > Hi everyone,
> >
> > I'm confused as to what version of NumPy this most recent release of
> > matplotlib wants to be used with - I get the following message:
> >
> > >>> from pylab import *
> > RuntimeError: module compiled against version 1000002 of C-API but
> > this version of numpy is 1000000
> > ...etc
> >
> > This suggests to me that my current version of numpy is out of date.
> > The most recent version of numpy on their sourceforge site is
> > apparently 0.9.8, and a beta version - 1.0b5
> >
> > Cheers,
> >
> > Dave
> >
> > -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, security?
> > Get stuff done quickly with pre-integrated technology to make your job easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
>

mpl 0.87.5 is compiled against numpy 1.0b5. It should remain
compatible with future release of 1.0.
On 9/15/06, David Andrews <irb...@gm...> wrote:
> Hi everyone,
>
> I'm confused as to what version of NumPy this most recent release of
> matplotlib wants to be used with - I get the following message:
>
> >>> from pylab import *
> RuntimeError: module compiled against version 1000002 of C-API but
> this version of numpy is 1000000
> ...etc
>
> This suggests to me that my current version of numpy is out of date.
> The most recent version of numpy on their sourceforge site is
> apparently 0.9.8, and a beta version - 1.0b5
>
> Cheers,
>
> Dave
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hi everyone,
I'm confused as to what version of NumPy this most recent release of
matplotlib wants to be used with - I get the following message:
>>> from pylab import *
RuntimeError: module compiled against version 1000002 of C-API but
this version of numpy is 1000000
...etc
This suggests to me that my current version of numpy is out of date.
The most recent version of numpy on their sourceforge site is
apparently 0.9.8, and a beta version - 1.0b5
Cheers,
Dave

John Hunter wrote:
>>>>>> "Volker" =3D=3D Volker Lorrmann <lor...@ph...> w=
rites:
>>>>>> =20
>
> Volker> Hi guys, how can i tell matplotlib to only show the xgrid
> Volker> (grid without y -lines ;) ) I=B4ve searched and googled a
> Volker> lot. But i can=B4t find a solution.
>
> You should be able to toggle the grid separately with
>
> ax.xaxis.grid(True)
> ax.yaxis.grid(False)
>
> Note that the grid command takes optional kwargs to control the major
> and minor tick gridding.
>
> JDH
> =20
Thanks for your help.
I=B4ve tried to work with axvline instead, but sadley avline can=B4t handle=
=20
vectors/arrays.
Volker
--=20
-----------------------
Volker Lorrmann
Universit=E4t W=FCrzburg
Experimentelle Physik 6
Am Hubland
97074 Wuerzburg
Germany
Tel: +49 931 888 5770
vol...@ph...