./www/py-WebOb, Python module providing WSGI request and response objects

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 1.8.6, Package name: py37-WebOb-1.8.6, Maintainer: kamelderouiche

WebOb provides wrappers around the WSGI request environment, and an
object to help create WSGI responses.

The objects map much of the specified behavior of HTTP, including
header parsing and accessors for other standard parts of the
environment


Required to run:
[devel/py-setuptools] [lang/python37]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 6e66b6cd2f37babb7fe13aef08e6c0df9926e42b
RMD160: b39c8545334e238d2f82bf17ae322eb4163a5577
Filesize: 268.17 KB

Version history: (Expand)


CVS history: (Expand)


   2020-05-17 22:18:36 by Adam Ciarcinski | Files touched by this commit (10)
Log message:
pytest from versioned depends
   2020-01-29 23:47:02 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-WebOb: updated to 1.8.6

1.8.6:

Experimental Features

- The SameSite value now includes a new option named "None", this is a new
  change that was introduced in
  https://tools.ietf.org/html/draft-west- … ntalism-00

  Please be aware that older clients are incompatible with this change:
  https://www.chromium.org/updates/same-s … e-clients, WebOb does
  not enable SameSite on cookies by default, so there is no backwards
  incompatible change here.

- Validation of SameSite values can be disabled by toggling a module flag. This
  is in anticipation of future changes in evolving cookie standards.
  The discussion in https://github.com/Pylons/webob/pull/407 (which initially
  expanded the allowed options) notes the sudden change to browser cookie
  implementation details may happen again.

  In May 2019, Google announced a new model for privacy controls in their
  browsers, which affected the list of valid options for the SameSite attribute
  of cookies. In late 2019, the company began to roll out these changes to their
  browsers to force developer adoption of the new specification.
  See https://www.chromium.org/updates/same-site and
  https://blog.chromium.org/2019/10/devel … r-new.html for more
  details on this change.
   2019-01-05 01:17:07 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-WebOb: updated to 1.8.5

1.8.5:
Warnings
- Fixed one last remaining invalid escape sequence in a docstring.
   2018-12-14 14:14:37 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-WebOb: updated to 1.8.4

1.8.4:

Bugfix
- Response.content_type now accepts unicode strings on Python 2 and encodes
  them to latin-1.
- Accept header classes now support a .copy() function that may be used to
  create a copy. This allows create_accept_header and other like functions
  to accept an pre-existing Accept header.

Warnings
- Some backslashes introduced with the new accept handling code were causing
  DeprecationWarnings upon compiling the source to pyc files, all of the
  backslashes have been reigned in as appropriate, and users should no longer
  see DeprecationWarnings for invalid escape sequence.

1.8.3:

Bugfix
- acceptparse.AcceptValidHeader, acceptparse.AcceptInvalidHeader, and
  acceptparse.AcceptNoHeader will now always ignore offers that do not
  match the required media type grammar when calling .acceptable_offers().
  Previous versions raised a ValueError for invalid offers in
  AcceptValidHeader and returned them as acceptable in the others.

Feature
- Add Request.remote_host, exposing REMOTE_HOST environment variable.
- Added acceptparse.Accept.parse_offer to codify what types of offers
  are compatible with acceptparse.AcceptValidHeader.acceptable_offers,
  acceptparse.AcceptMissingHeader.acceptable_offers, and
  acceptparse.AcceptInvalidHeader.acceptable_offers. This API also
  normalizes the offer with lowercased type/subtype and parameter names.
   2018-07-26 12:38:12 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-WebOb: updated to 1.8.2

1.8.2:
Bugfix
- SameSite may now be passed as str or bytes to Response.set_cookie and
  cookies.make_cookie. This was an oversight as all other arguments would be
  correctly coerced before being serialized.
   2018-05-16 09:57:06 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
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.
   2017-11-28 09:55:48 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-WebOb: updated to 1.7.4

1.7.4:
Feature
Add support for wsgi.input_terminated in the wsgi environ to allow for Chunked \ 
Encoding to be used with WebOb
   2017-07-11 09:24:04 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
1.7.3:
Bugfix
- Request.host_url, Request.host_port and Request.domain now all understand and
  know how to parse IPv6 Host headers sent by browsers.