Remove loose print statement and fix future warning

[adybbroe]

Signed-off-by: Adam.Dybbroe [email protected]

Fixing issue 345. A loose print statement is removed. And a future warning from xarray is dealt with in the ears-nwc reader

• Closes Future warning - xarray #345
• Tests passed
• Passes git diff origin/master **/*py | flake8 --diff

[adybbroe]

I have removed the print statement that affected all readers. But not yet looked at the warning from xarrat

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@bc87fed). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master     #352   +/-   ##
=========================================
  Coverage          ?   70.27%           
=========================================
  Files             ?      123           
  Lines             ?    17436           
  Branches          ?        0           
=========================================
  Hits              ?    12253           
  Misses            ?     5183           
  Partials          ?        0

Impacted Files	Coverage Δ
satpy/readers/__init__.py	95.62% <ø> (ø)
satpy/readers/nc_nwcsaf.py	17.02% <0%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bc87fed...d3b30a8. Read the comment docs.

[djhoese]

@adybbroe Do you have an example of the future warning? Maybe someone else could look at the warning and fix it so that we could merge this for 0.9.1.

Edit: Nevermind, I found your example output in your issue.

[djhoese]

FYI I found at least one small future warning in the viirs l1b reader where I was doing if 'dim_0' in data: and now it needs to be if 'dim_0' in data.dims: because in the future it will search the values of the data array which is not what we want. Maybe your future warning is something similar, but I haven't actually looked. I will make a pull request for my warning's fix in the next couple days hopefully.

[djhoese]

@adybbroe If you have a chance to test this that would be great. The xarray related warnings should be fixed now. If you don't get to it before the tests pass I'll just merge it anyway and if you still have the warning we'll open the issue up again.