Fix sphinx docs generation after setuptools_scm migration #943
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working on #586 I noticed that the sphinx docs had a lot of unnecessary warnings. This PR fixes those warnings and all flake8 docstring issues that occurred in the files that needed to be changed.
Note that even with these changes you get these warnings from sphinx:
Obviously the top two are from me not having pygrib installed, but the others are from us having readers (and resampling) re-documented in the readers sphinx page and the resample sphinx page. I know the readers were something that @mraspaud wanted because it provides a nice list and summary of the readers, but this seems to be confusing sphinx. Maybe this will be fixed when we think about auto-generating a reader table based on the metadata in the reader YAML file.
flake8 satpy