On Jul 8, 2010, at 12:16 PM, John Hunter wrote: > On Thu, Jul 8, 2010 at 11:13 AM, Tony S Yu <tsy...@gmail.com> wrote: >> The recent "nasty import behavior" thread motivated me to post an issue I've >> been having with matplotlib and chaco. (I've posted to the Chaco list >> previously, without much luck.) >> >> If I import matplotlib and chaco at the same time, I get a segmentation >> fault in the _path.so plugin. Below is a simple script that segfaults on my >> computer. >> >> I should note that this is installation dependent; someone on the Chaco list >> only had the issue with certain versions of Python. Just for reference, I'm >> on OS X 10.6, Python 2.6.1, and matplotlib/chaco trunk. >> >> -Tony >> >> P.S. In reality, there's no reason to import matplotlib when using Chaco, >> but I have some helper modules with some tangled imports (i.e. need to be >> refactored). > > First question -- are you compiling both yourself and are they > compiled against the same version of numpy. If not, I suspect we are > seeing a numpy version conflict.
I am compiling both myself. I did clean compiles of both when Numpy had the whole ABI change (and change back). I've recompiled since then, but without cleaning out compiled code. I can try clean builds, but that will have to be later in the day. I'll post an update. Thanks, -Tony ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
