-
Notifications
You must be signed in to change notification settings - Fork 44
Fix build #270
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
Merged
Merged
Fix build #270
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
665df60
add badges (#268)
bjlittle 99d4344
Fix Iris dev guide link (#267)
TomDufall 3fddc50
Fix nox when HOME not set
TomDufall 64e07ad
Remove removed Iris util
TomDufall 8cdf705
Revert "Fix nox when HOME not set"
TomDufall 1640670
Actually remove the import
TomDufall a8e495a
Remove another use of _array_slice_ifempty
TomDufall 08c4a2f
Fix visual alignment of continuation
TomDufall c536e49
Remove test for removed functionality
TomDufall 050233d
Force retest
TomDufall File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm just wondering if it would make sense to leave this in as a "regression" testcase ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A difficult question! Maybe side with caution and leave it in? We can remove it later on if it causes problems.
On a side note I think we should ASV (aka performance) testing for this sort of thing. I had started thinking about it last week after SciTools/iris#4141.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok sorry I didn't read this closely enough.
This test will now fail, as we no longer intercept zero-length slicing.
You could modify it to call iris._lazy_data._as_lazy_data + check that that didn't 'visit' the data, but that's really testing Iris (which we do elsewhere), so not really appropriate here.
So, let's scrap it, as you originally suggested. 👍