MAINT: remove uses of np.testing.rand #5663
Merged
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.
a follow-up to #5661.
Having
np.testing.rand
likely made sense in 2002 (was it scipy_core.testing.rand then?), but not so much now that we rely onnumpy.random
almost everywhere.These have not been reported as causing immediate trouble, so these probably can be just treated as a regular maintenance, unlike gh-5661 which is a backport material.