-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Resolve warnings issued in the xarray test suite #1652
Comments
Do I understand right that you'd like to silence the warnings in the |
Yes, I don't think this warning is very useful -- pandas doesn't show it. |
Right, I misunderstood that part. |
👍 on squashing as many of these as possible. |
I'll take this one on unless someone else really wants it. |
reopening since #1657 only took care of a subset of the current warnings. |
Here's the latest output (excluding EDIT: put this into a details dropdown
|
In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here or remove the |
this may be related to (or superseded by) #3266 |
closing in favor of #3266 |
82 warnings are currently issued in the process of running our test suite:
https://gist.github.com/shoyer/db0b2c82efd76b254453216e957c4345
Some of can probably be safely ignored, but others are likely noticed by users, e.g.,
https://stackoverflow.com/questions/41130138/why-is-invalid-value-encountered-in-greater-warning-thrown-in-python-xarray-fo/41147570#41147570
It would be nice to clean up all of these, either by catching the appropriate upstream warning (if irrelevant) or changing our usage to avoid the warning. There may very well be a lurking FutureWarning in there somewhere that could cause issues when another library updates.
Probably the easiest way to get started here is to get the test suite running locally, and use
py.test -W error
to turn all warnings into errors.The text was updated successfully, but these errors were encountered: