On 11/10/2011 05:16 PM, Friedrich Romstedt wrote: > Furthermore, Michael is right, while bisecting I didn't ``rm build/`` > properly; I just did ``python2.6 setup.py clean``. Later on I did that > properly, after I noticed that the offending commit reported by bisect > actually runs cleanly. I then wrote a test script for ``git bisect > run`` that applies all those steps, so I couldn't keep forgetting it > any longer :-) Friedrich Running bisect in this way, did you arrive at a more conclusive determination about which commit may have introduced the problem?
Mike ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
