Le 7 avril 2012 13:18, Andreas Mueller <[email protected]> a écrit : > On 04/07/2012 01:14 PM, Olivier Grisel wrote: >> This looks like a nose doctest plug-in bug. Would be great if someone >> could extract a scikit-learn independent reproduction case and report >> it to the nose project. >> > This is a known bug in the Numpy Nosetester that was recently fixed. > see https://github.com/scikit-learn/scikit-learn/issues/665 > https://github.com/nose-devs/nose/issues/507#issuecomment-4707862 > > Maybe we should include this in the docs?
Well it stems from a real doctest bug IMHO: https://code.google.com/p/python-nose/issues/detail?id=445 If someone want to submit a pull request from the above report to nose that might help speedup the fix in nose directly. Alternatively we could backport the numpy fix as a monkeypatch in sklearn.utils.fixes and use it for handling the tests. -- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
