I have seen that message, but I wasn't sure these errors were directly connected since he mentions of getting segfaults whereas in my case only gives import errors. Building a new copy of scipy fixed this error.
On Wed, Oct 7, 2009 at 10:10 AM, Robert Kern <robert.k...@gmail.com> wrote: > On Wed, Oct 7, 2009 at 09:55, Gökhan Sever <gokhanse...@gmail.com> wrote: > > Hello, > > > > I checked-out the latest trunk and make a new installation of NumPy. My > > question: Is it a known behaviour that this action will result with > > re-building other packages that are dependent on NumPy. In my case, I had > to > > re-built matplotlib, and now scipy. > > Known issue. See the thread "Numpy SVN broken". > > -- > Robert Kern > > "I have come to believe that the whole world is an enigma, a harmless > enigma that is made terrible by our own mad attempt to interpret it as > though it had an underlying truth." > -- Umberto Eco > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > -- Gökhan
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion