Add metpy #1
Add metpy #1
Conversation
This way there isn't disagreement between what's at the top of the config and what's used later.
This is a community developed channel that will have more packages available.
|
Bounced to re-trigger tests since metpy master got fixed. |
dopplershift
force-pushed
the
add-metpy
branch
from
98b465e
to
5575138
Compare
|
@dopplershift and @zbruick, based on a recent comment by @hgrecco (hgrecco/pint#878 (comment)) would you think this would be worth updating? I think this would serve a similar purpose to the build added in Unidata/MetPy#1144, but more visible from pint's end than from MetPy's? |
|
Not sure what is involved in updating this (defer to @dopplershift and @hgrecco) but I'm +1 for us not having to worry as much about responding to upstream dependency changes if breaking us (and other downstream packages) can be avoided through testing like this. |
|
I still think this PR is a good idea. I'm not sure what's needed to update here. I still want our own internal builds so that we get early warning. |
|
bors r+ |
1 similar comment
|
bors r+ |
I also took the liberty of cleaning a few things about the Travis config. Apologies if that's not acceptable.