py-WebOb: updated to 1.8.1

1.8.1:

Bugfix
- acceptparse.MIMEAccept which is deprecated in WebOb 1.8.0 made a backwards
  incompatible change that led to it raising on an invalid Accept header. This
  behaviour has now been reversed, as well as some other fixes to allow
  MIMEAccept to behave more like the old version.

1.8.0:

Feature
- request.POST now supports any requests with the appropriate
  Content-Type. Allowing any HTTP method to access form encoded content,
  including DELETE, PUT, and others.

Compatibility
- WebOb is no longer officially supported on Python 3.3 which was EOL'ed on
  2017-09-29.

Backwards Incompatibilities
- Many changes have been made to the way WebOb does Accept handling, not just
  for the Accept header itself, but also for Accept-Charset, Accept-Encoding
  and Accept-Language.
- When calling a @wsgify decorated function, the default arguments passed
  to @wsgify are now used when called with the request, and not as a
  start_response
- When setting app_iter on a Response object the content_md5 header
  is no longer cleared. This behaviour is odd and disallows setting the
  content_md5 and then returning an iterator for chunked content encoded
  responses.

Experimental Features
These features are experimental and may change at any point in the future.
- The cookie APIs now have the ability to set the SameSite attribute on a
  cookie in both webob.cookies.make_cookie and
  webob.cookies.CookieProfile.

Bugfix
- Exceptions now use string.Template.safe_substitute rather than
  string.Template.substitute. The latter would raise for missing mappings, the
  former will simply not substitute the missing variable. This is safer in case
  the WSGI environ does not contain the keys necessary for the body template.
- Request.host_url, Request.host_port, Request.domain correctly parse IPv6 Host
  headers as provided by a browser.
- Request.authorization would raise ValueError for unusual or malformed header
  values.
- Allow unnamed fields in form data to be properly transcoded when calling
  request.decode with an alternate encoding.
- Response.__init__ would discard app_iter when a Response had no
  body, this would cause issues when app_iter was an object that was tied
  to the life-cycle of a web application and had to be properly closed.
  app_iter is more advanced API for Response and thus even if it
  contains a body and is thus against the HTTP RFC's, we should let the users
  shoot themselves by returning a body.

0 files changed, 0 insertions, 0 deletions