[SciPy-Dev] update on 0.11.0 status
Sun Jul 15 18:49:01 CDT 2012
Good catch, Ralf!
Initializing all values of dist_array to zero is the correct thing to do
here. I don't know how I missed that...
On 07/15/2012 07:57 AM, Ralf Gommers wrote:
> On Wed, Jul 11, 2012 at 11:45 PM, Ralf Gommers
> <firstname.lastname@example.org <mailto:email@example.com>> wrote:
> On Tue, Jul 10, 2012 at 11:33 PM, Jake Vanderplas
> <mailto:firstname.lastname@example.org>> wrote:
> I tried running valgrind on the offending code. I don't see
> anything out of the ordinary come up on my system (for
> reference, the scikit-learn developer documentation has some
> tips on using valgrind for cython code ). This makes me
> suspect that the error you're seeing may be a system-specific
> issue (i.e. 32 bit/64 bit mismatch), or perhaps something
> related to the numpy version (I'm using the current numpy
> Could you run valgrind on your system with
> test_shortest_path.py and see if anything obvious comes up?
> It's clean, some noise related to Python itself but nothing
> related to csgraph.
> This was 32-bit python 2.6, numpy 1.8-dev by the way. I haven't
> yet checked if I get the same when running in 64-bit mode on the
> same machine yet.
> Found the issue (use of an array created with np.empty), see
> SciPy-Dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev