-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Avoid use of deprecated get= parameter in tests #2500
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
Conversation
The get= keyword has been deprecated and will be removed in a future version.
Thanks @mrocklin Anyone have any idea why Travis isn't running? Is it the GH issues from this morning? Looks like the latest run was a couple of days ago: https://travis-ci.org/pydata/xarray/pull_requests |
Yes, github is still having issues. https://status.github.com/messages
We are working through the backlogs of webhook deliveries and Pages builds.
We continue to monitor as the site recovers.
…On Mon, Oct 22, 2018 at 2:48 PM Maximilian Roos ***@***.***> wrote:
Thanks @mrocklin <https://github.com/mrocklin>
Anyone have any idea why Travis isn't running? Is it the GH issues from
this morning? Looks like the latest run was a couple of days ago:
https://travis-ci.org/pydata/xarray/pull_requests
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2500 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AASszMBivzvQsiHHkWkGP2F2kYaafzmeks5unhLggaJpZM4Xz6dG>
.
|
Hello @mrocklin! Thanks for submitting the PR.
|
I'm not sure that I understand the failure here. Can someone verify that this is related to these changes?
|
I'm pretty sure that error is different, cc @alexamici |
thanks @mrocklin ! |
@shoyer you are right, I had to make a user-visible backward-incompatible change in cfgrib and Travis is getting the latest version. I'll make a PR to fix the test. Note that I don't expect to do any other backward-incompatible change this big and the test is going to be robust to version change from now on. |
whats-new.rst
for all changes andapi.rst
for new API (remove if this change should not be visible to users, e.g., if it is an internal clean-up, or if this is part of a larger project that will be documented later)