-
Notifications
You must be signed in to change notification settings - Fork 297
Reinstate iris_grib. #2810
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
Reinstate iris_grib. #2810
Changes from all commits
7e5f085
5860f7f
f48b51a
fc0c21f
3ed870e
28828da
3df9b87
fd36e9d
7d0cced
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -65,6 +65,16 @@ install: | |
fi | ||
fi | ||
|
||
# JUST FOR NOW : Install latest master version of iris-grib. | ||
- if [[ "$TEST_MINIMAL" != true ]]; then | ||
INSTALL_DIR=$(pwd) ; | ||
wget https://github.com/SciTools/iris-grib/archive/master.zip ; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These lines could be replaced with |
||
unzip -q master.zip ; | ||
cd iris-grib-master ; | ||
python setup.py install ; | ||
cd - ; | ||
fi | ||
|
||
- PREFIX=$HOME/miniconda/envs/$ENV_NAME | ||
|
||
# Output debug info | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -34,3 +34,6 @@ nc_time_axis | |
pandas | ||
python-stratify | ||
pyugrid | ||
|
||
# Iris extensions (i.e. key tools that depend on Iris) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Defines a concept of "Iris extensions" What we found is that these :
|
||
# iris_grib |
Uh oh!
There was an error while loading. Please reload this page.
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.
Aren't we going to have to do this every time we change the Iris API in a way that breaks the currently released iris-grib? Additionally, when that happens we need to make sure we fix iris-grib at the same time to keep the Iris tests passing. I can't help thinking we need to break the circular dependency. That would mean no Iris tests which use iris-grib
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.
Alternatively: Make Iris-grib no longer depend on Iris somehow.
Uh oh!
There was an error while loading. Please reload this page.
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.
Well yes, but that shouldn't really be any more frequent than breaking changes to user code.
That is, if Iris-Grib only depended on Iris public api.
That should be perfectly practical -- and right now is nearly true -- but unfortunately still a way off.
I'm working on that = main reason why this PR is not yet ready.
I think we can + will still have tests that use iris-grib in an integration-type way, but we will remove anything depending on iris-grib internals. Again it's WIP.
Iris will still need to use dynamic import of iris-grib, to avoid circularity in testing.
Really not practical I think. But we certainly can ensure that Iris does not depend on Iris-grib.
We should ensure that :
At this point, the hard part is still the tests :
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.
Correction : that would be nice, but is not required for Iris 2.0 release, so I'm shelving it for now.
See iris-grib#88