Conversation
|
Resolved the merge conflict in the whats new file. |
|
@bmu or @Calama-Consulting are we good to go on this one? |
|
Ooops, maybe I was to hasty. When I run the tests without scipy I get for errors:
Not sure, where the errors are thrown in all cases (I don't see any use of ineichen or scipy in I think we should skip all tests that use scipy, if scipy is not installed. |
|
Ok, that was very confusing but I tracked it down to The nosetests log now looks right to me. I agree that we should skip the tests that require scipy if scipy is not installed, however, I would suggest that we make that a 0.2 milestone. |
|
Ah, not sure what the best git approach is here, but I ended up making a new PR in #34 to resolve this. |
As discussed in #13.
I briefly looked into adding a real test for this, but it wasn't immediately obvious how to do it. Instead, I ran the test suite on a virtualenv without scipy. Here's the output, as expected: