Fixed some type mismatches in case when mtom/xop is in incoming message #716
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'm building simple SOAP-service with
Spyne 2.14
and a SOAP-client withZeep 4.3.1
+pymtom_xop 0.0.2
onPython 3.10
as part of my university's homework.I've faced the problem using
Spyne
for handling incomingMTOM/XOP
attachments. There were multiple not handled exceptions, generally because of types mismatching and not-declared variables. I'm wondering how linter skipped such mistakes, anyways...I tried my best to catch and handle them, so now it works almost fine. I still receive HTTP 500 for mp3 files (yeah, very strange), but for now I'll leave it as is 🫤