Closed verduijn closed 1 month ago
Thanks for the feedback!
I figured that check_satpy
was in the default issue template, so it could be useful to have the versions information in there.
From there:
show_versions
functionality itself without much downsidecheck_satpy
was flexible with extras
so I just did the sameextras
and packages
was essentially the same I just renamed itrounding up I think we should either:
show_versions
and add it, with hardcoded packages, in check_satpy
show_versions
function and reverting the check_satpy
function if it's not desirable to add the versions in check_satpy
.Good point with it being in the issue template. We wouldn't want users to have to run multiple things to show similar information. In that case I agree that the versions after the readers/writers in check_satpy
does make more sense than the "ok" that is there now. Ok I'm coming around. Thanks for explaining your reasoning.
I guess it's ready for review?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 96.05%. Comparing base (
9e3b342
) to head (692c9b1
). Report is 79 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
satpy/composites/config_loader.py | 2 | 94.12% | ||
satpy/tests/utils.py | 2 | 93.16% | ||
satpy/tests/reader_tests/gms/test_gms5_vissr_l1b.py | 3 | 98.67% | ||
satpy/tests/reader_tests/gms/test_gms5_vissr_navigation.py | 3 | 97.18% | ||
satpy/readers/msi_safe.py | 4 | 98.41% | ||
<!-- | Total: | 14 | --> |
Totals | |
---|---|
Change from base Build 10957325874: | -0.01% |
Covered Lines: | 52564 |
Relevant Lines: | 54668 |
MR to add
show_versions
tosatpy.utils
to allow for use insatpy.utils.check_satpy
. Use case is to help in figuring out run-time environment factors while debugging issues.