Log Message:
py-multipart: updated to 1.1.0

Release 1.1

This release could have been a patch release, but some of the fixes include \ 
change in behavior to match documentation or specification. None of them should \ 
be a surprise or have an impact on real-world clients, though. Existing apps \ 
should be able to upgrade without issues.

fix: Fail faster on input with invalid line breaks
fix: Allow empty segment names
fix: Avoid ResourceWarning when using parse_form_data
fix: MultipartPart now always has a sensible content type.
fix: Actually check parser state on context manager exit.
fix: Honor Content-Length header, if present.
perf: Reduce overhead for small segments (-21%)
perf: Reduce write overhead for large uploads (-2%)

Release 1.0

This release introduces a completely new, fast, non-blocking  \ 
PushMultipartParser parser, which now serves as the basis for all other parsers.

feat: new PushMultipartParser parser.
change: Parser is stricter by default and now rejects clearly broken input. This \ 
should not affect data sent by actual browsers or HTTP clients, but may break \ 
some artificial unit tests. * Fail on invalid line-breaks in headers or around \ 
boundaries. * Fail on invalid header names.
change: Default charset for segment headers and text fields changed to utf8, as \ 
recommended by W3C HTTP.
change: Default disk and memory limits for MultipartParser increased, but \ 
multiple other limits were introduced to allow finer control. Check if the new \ 
defaults still fit your needs.
change: Several undocumented APIs were deprecated or removed, some of which were \ 
not strictly private but should only be used by the parser itself, not by \ 
applications.