Open gerritholl opened 2 years ago
You are right that they need to be updated. I'm not sure explicitly excluding them from available_readers imports is the best idea as we may forget and if/when the reader is updated they won't be shown in available_readers.
Looking closer though, it looks like these tracebacks are actually DEBUG log messages, right?
I just was asked to try the caliop reader and came across this error. So the conclusion is the caliop reader is officially not supported?
@joleenf Correct. The reader was never updated to work with xarray/dask.
Describe the bug
When I call available_readers(), Satpy outputs several tracebacks where imports fail due to yaml.ConstructorError being raised.
To Reproduce
Expected behavior
I expect no error messages.
Actual results Text output of actual results or error messages including full tracebacks if applicable.
Environment Info:
from satpy.utils import check_satpy; check_satpy()
]Additional context
The failing readers appear to be not covered by unit tests, or this would come up during unit testing. If those readers are currently unsupported, which I think they are, then probably they should be explicitly excluded as such. When users following satpy documentation call
available_readers()
and are presented with multiple tracebacks, they may think something is wrong.