[SciPy-Dev] update on 0.11.0 status
Mon Jul 16 13:34:53 CDT 2012
On Mon, Jul 16, 2012 at 1:49 AM, Jake Vanderplas <
> 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...
Great, thanks for confirming.
Now that all issues have fixes available, I plan to merge all open PRs by
tomorrow and prepare a release candidate asap. Some PRs haven't been
reviewed yet but they're very straightforward - please have a look at them
or let me know you intend to do so if you want me to wait.
> 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> wrote:
>> On Tue, Jul 10, 2012 at 11:33 PM, Jake Vanderplas <
>> email@example.com> 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
> SciPy-Dev mailing listSciPy-Dev@scipy.orghttp://mail.scipy.org/mailman/listinfo/scipy-dev
> SciPy-Dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev