RF: Pull compression detection logic into a central private module #1212
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.
This change is motivated by a change in
pyzstd
, which exposes failures to read bad streams as customZstdError
s instead ofOSError
s. We had previously been depending on a conflation of these, asBZ2File
returns a straightforwardOSError
andGzipFile
returnsBadGzipFile
, which subclasses fromOSError
.Now there's no clear way of catching the various ways that reading a stream might fail without creating a collection of exceptions and adding to it when an interface that emits different errors is found.
Therefore, I've created a private
nibabel._compression
module. This housesopeners.COMPRESSED_FILE_LIKES
and aliasesIndexedGzipFile
toGzipFile
when it is unavailable, as well as provides a newCOMPRESSION_ERRORS
exception type tuple that can be used inexcept
statements.Fixes #1209.