Eric Firing <efir...@...> writes:

> 
> Dave wrote:
> > I upgraded my numpy to 1.4.0.dev7375 and scipy to 0.8.0.dev5920. After 
> > doing so I get a segfault upon calling the plot command (see below)
> 
> What happens if you simply do
> 
> x = randn(100) 
>
> or
>
> plot([1,2,3,2,1])
> 
> 
> My guess is that you are seeing a numpy installation problem, not a 
> matplotlib problem (that is, I expect the first trial above to fail and 
> the second to succeed), and that the problem may be that you did not 
> delete the build directory before rebuilding numpy from source. 
> Distutils often fails to rebuild components that need to be recompiled 
> after a change to the source, so the build and install appear to work, 
> but the resulting numpy (or matplotlib, for that matter) does not.
> 
> Eric
> 

I initially had problems with numpy/scipy as I forgot to delete the build
directories. After doing so & recompiling they both passed all tests (barring
some known issues with windows & arctan -
http://article.gmane.org/gmane.comp.python.numeric.general/31967)

x = randn(100) worked fine and returned expected results for .mean() and .std()
the segfault only occurred upon calling the plot(x).

I resolved the issue by compiling matplotlib from source on my windows box 
which I'm happy to report wasn't too difficult! It seems to work for my usual
interactive use however it segfaults when running the tests :|

http://pastebin.com/m5ee30885

HTH,
Dave


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Reply via email to