replace gdal exceptions decorator with context manager #400
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I noticed that a bunch of functions were missing from the pygeoprocessing API docs, and it's because of the decorator I introduced in #392. The functions returned from the decorator don't have the docstring of the original, so no docs were generated.
This was the last straw - since I ran into other issues with the decorator before with multiprocessing and pickling, I decided to remove it and use the reliable context manager everywhere. The extra indentation is annoying in a few places, but this should be a temporary situation until we adopt GDAL 4.