forked from scipy/scipy
-
Notifications
You must be signed in to change notification settings - Fork 0
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
WIP: Doctest ng #11
Closed
Closed
WIP: Doctest ng #11
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
Patch up refguide-check to record the history; switch off checking rst files
Check that all objects are included. Patch up both refguide-check and doctest_public_modules to emit the history, and compare them, e.g. $ meld tools/doctest.log refguide-check.log The logs are *identical* modulo `stats.kstwobign` and `stats.levy_stable` which were excluded in refguide-check but this seems to be no longer needed.
$ python dev.py doctest -t absolute/path/to/file.py
This matches the refguide-check behavior, but is a tad strange: makes sure that the seed the old-fashioned np.random* methods is *NOT* reproducible but the new-style `default_rng()` *IS* repoducible. Should these two be either both repro or both not repro?
Add missing imports, now that we explicitly require them.
They use an implicit numpy imports, which SciPy does not anymore. So skip them, it's not SciPy job to worry about, really.
The docstring manipulates warnings, and that interferes with the doctester. Maybe this is something to fix in the doctester itself, not the docstring.
The tweaks are: - the Octave version is different (somebody forgotten to check in regenerated files, in 2013) - the dict order is different, at least on python 3.8
ev-br
force-pushed
the
doctest_ng
branch
2 times, most recently
from
February 18, 2024 16:00
43ecf92
to
10996cc
Compare
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.
Reference issue
What does this implement/fix?
Additional information