-
Notifications
You must be signed in to change notification settings - Fork 528
[MRG] Have Travis actually execute doctests #90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
At the moment, I have:
I have not fixed bugs related to numpy array formatting, let me know which version of formatting I should use or if there is a clever way to deal with those in doctests. Also, there are the following tests that do not pass and that would need checking:
Should I add this as a member in
Could someone check if those values are reasonable?
This test definitely fails: is it the test that is wrong or the value returned by POT? |
…tested in tests/)
OK, things should be (close to) OK now, with tests executed and passing. By the way, there was a bug in |
This is awesome, thank you @rtavenar I see no problem in the code and will do the merge. |
Hi there,
As it is coded at the moment, doctests are not checked by Travis, since the call in
test_ot
does not raise any error. This PR is an attempt to fix that.