[SciPy-Dev] update on 0.11.0 status
Sun Jul 15 09:57:02 CDT 2012
On Wed, Jul 11, 2012 at 11:45 PM, Ralf Gommers
> On Tue, Jul 10, 2012 at 11:33 PM, Jake Vanderplas <
> 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 1.8.0-dev).
>> 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
> 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
Found the issue (use of an array created with np.empty), see
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev