Refactor parser logic to better allow subclassing #77
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 tries to fix #73 by moving all general purpose parser logic out of
MultipartSegment
back into the parser where it belongs and isolatingform-data
specific checks into a private parser method which can be overridden. Developers can now subclassPushMultipartParser
and override_create_segment(self, headerlist)
to support other multipart stream types (e.g.multipart/byterange
ormultipart/mixed
) if necessary.The change has a minimal impact on performance and actually performs better for the relevant use cases (large forms or large uploads).