Make tests optional that depend on pydot and pandas (optional installs).#479
Make tests optional that depend on pydot and pandas (optional installs).#479rhattersley merged 1 commit intoSciTools:masterfrom
Conversation
|
Re: recent change (pp-mo@d9451c3) |
|
The generalised version is certainly clever, but I'm not sure it's worth it since there's still quite a lot of boilerplate left in the client module. How about if the client code (e.g. iris.tests.test_pandas) just did: I'd have more time for the generalised version if it could be used more like: |
|
Thanks @rhattersley . But you're reading my mind now... That's just the thought process I've been going through since pushing this (which I now wish I hadn't). |
I'm tending to agree, and I think it's more obvious to leave the workings visible in the test file. |
lib/iris/tests/test_file_save.py
Outdated
There was a problem hiding this comment.
Could this be simplified to just unittest.skipIf(...) with a condition clause based on dot.DOT_AVAILABLE?
There was a problem hiding this comment.
Or perhaps ditch DOT_AVAILABLE altogether since it's only used here and just test the executable path directly.
|
That's a nasty catch in the new licence header checks |
|
Thanks @rhattersley, @esc24 . |
👍 Looks good enough for me (at cfdd8483dc559e969ddd7fa26795dc5908deb9a6). Please squash and I'll merge. |
Thanks, done that. All re-tested, should be ok this time. |
|
Thanks @pp-mo. 😄 |
Make tests optional that depend on pydot and pandas (optional installs).
|
Great stuff @pp-mo. These kind of contributions, although not the most exciting features to work on, are really important. |
Failed on these in my amazon instance VM.
We could probably do with an "official" list of what installs developers should use?
See also #478 -- but possibly this should have gone on discussion groups instead??