fix: IndexError when empty body response #1287
Open
Conversation
This file contains hidden or 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
timboode
approved these changes
Sep 26, 2025
There was a problem hiding this comment.
@mvantellingen We are running into this issue in our corporate environment. We have confirmed that the fix contained within this PR solves the index out of bounds issue. Any chance we can get this merged with the next zeep version?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
When there is no body element in the response, zeep is throwing an
IndexErrorbecause there is eventually 0xmlelement.Changes Made
Added check for the not empty
xmlelementinDocumentMessage._deserialize_body