On 09/15/2010 03:50 AM, Benjamin Root wrote: > On Wed, Sep 15, 2010 at 5:34 AM, Dan Kortschak > <dan.kortsc...@adelaide.edu.au <mailto:dan.kortsc...@adelaide.edu.au>> > wrote: > > I've just has a look at that and unfortunately it does not fix the > problem > > Is there any other suggestion that might be worth a try? > > I should point out that I already have numpy 1.4.1 installed and scipy > 0.8.0 as dependencies for other packages. > > thanks > Dan > > > Hmm, that shouldn't be an issue. Maybe you need to completely clean out > the matplotlib build (by removing the build directory) and try again? > Be sure to save the build output so we can see what happens if/when it > fails.
Looking again at the original build output, and at setup.py and setupext.py, it appears that there is a bug in the latter. If the wrong version of wx is found, it should be disabling the attempt to build wxagg, and reporting "wxPython: no". We need to fix the bug, but the workaround for now is to use a setup.cfg file with wxagg = False Eric > > Ben Root > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > > > > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-users ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
