-
Notifications
You must be signed in to change notification settings - Fork 395
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
Doctest configuration optionflags. Enhancement. #7
Comments
Correct patch. Google Code Info: |
Google Code Info: |
I applied the patch here http://bitbucket.org/kumar303/nose-doctest-306/ I also added unit and functional tests and amended the documentation. There are two Google Code Info: |
Has there been any progress on this? This would singlehandedly make nose actually useful with doctests. Thanks. :) Google Code Info: |
Applying this patch to nose 1.1.2 seems to work fine on my system. I have a project with hundreds of doctests, and the nose plugin to PyDev/Eclipse became much more useful with the patch. Google Code Info: |
NLTK, the Natural Language ToolKit for Python uses a lot of doctests that need +ELLIPSIS and/or +NORMALIZE_WHITESPACE. We have successfully been running our tests with this patch. Would love to see this applied in master so we don't have to bundle a patched version of nose to run our test suite… |
This patch would really be great for scikit-learn, too. Does anyone plan on including this or do we have to monkey-patch? |
Oh, it looks like this was merged. is that right? |
Yeah, this is in 1.2.1, unless I've done something very wrong. |
It would be useful to allow users to specify doctest option flags such as +ELLIPSIS or
+NORMALIZE_WHITESPACE in the configuration file and/or on the command line.
Attached is a patch that permits this with the added option --doctest-options which accepts a
comma separated list of option flags such as "+ELLIPSIS,+NORMALIZE_WHITESPACE".
Google Code Info:
Issue #: 306
Author: [email protected]
Created On: 2009-11-12T02:05:06.000Z
Closed On:
The text was updated successfully, but these errors were encountered: