ENH: add a three-state verbosity level : 0, 1, 2 in testmod #31
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
0 is failures only; 1 is emit object names just before doctesting; 2 is full, emit all examples.
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.
cross-ref gh-14
Emitting dots or F does not seem to play very nice with the doctest structure --- it requires to have two separate streams, one to capture the doctest reports, and the other for for '...F....'. It feels like it's going to evolve into an inferior homemade pytest clone, so pass on it for now and only use three levels: 0 is failures only; 1 is emit object names just before doctesting; 2 is full, emit all examples.
Let's see how this fares on larger workloads (scipy then numpy).
Note that it's a job for a testmod-like wrapper, because DTRunner's
report_*hooks work per-example, not per-docstring.