Hi, thanks for that script. It seam very useful for that case. As other people know about this problem, I won't need to bisect. thanks Fred On Mon, Sep 24, 2012 at 6:52 PM, Pauli Virtanen <pav@iki.fi> wrote:
25.09.2012 00:55, Frédéric Bastien kirjoitti:
On Mon, Sep 24, 2012 at 5:47 PM, Charles R Harris [clip]
I think this problem has been brought up on the list. It is interesting that it turned up after the first beta. Could you do a bisection to discover which commit is responsible?
I'll check that. Do I need to reinstall numpy from scratch everytimes or is there a better way to do that?
Reinstallation is needed, but this is reasonably simple to automate, check "git bisect run". For instance like so:
https://github.com/pv/scipy-build-makefile/blob/master/bisectrun.py
-- Pauli Virtanen
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion