Doctests to nosetests #16
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It seems like the py 2.6 version of the test framework doesn't have assertListEqual but I think we could make it work by adding unittest2 to our deps and using that (I think?). |
|
blrub. My autoenv is broken and I haven't fixed it. Should have caught that. Let's do this the easy way. Ie just == and call it a day. I was just trying to be fancy. |
|
Doing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move almost all doc tests to unit tests that are the run through nosetest instead of a custom script. When run in travis, we wiil use the --logging-level=INFO and --detailed-errors.