ensure uncertainties does not depend on numpy #2001
Merged
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
|
you'll need to run the linter or add a line the failing test_issue1611 might need to be have requires_uncertainties |
CodSpeed Performance ReportMerging #2001 will not alter performanceComparing Summary
|
tgbugs
force-pushed
the
fix-unc-np-coupling
branch
from
9d28d65
to
f9b969f
Compare
fix import ordering to ensure that uncertainties can be used without numpy, before this the check assumed that numpy was always installed update test_issue1611 to use requires_numpy since uncertainties and numpy are now decoupled
tgbugs
force-pushed
the
fix-unc-np-coupling
branch
from
f9b969f
to
73a4174
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.
Fix import ordering to ensure that uncertainties can be used without numpy, before this the check assumed that numpy was always installed.