Raise EOFError when seeking too far in PSD #9388
Open
+8
−0
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.
If you open a PSD file, use
n_frames, and then seek too far, anEOFErroris raised as expected.As the trace says, this is raised by
_seek_check(), because_n_frameshas been populated.However, if you do not use
n_frames, anIndexErroris raised instead.This is because PsdImagePlugin itself does not have any explicit handling for when you seek too far. This PR adds it, changing the second scenario to also raise an
EOFError.