Skip to content

Commit

Permalink
Update HISTORY.txt
Browse files Browse the repository at this point in the history
  • Loading branch information
@digitalresistor
digitalresistor committed Nov 21, 2016
1 parent 9207d5f commit bc024c8
Showing 1 changed file with 44 additions and 47 deletions.
91 changes: 44 additions & 47 deletions HISTORY.txt
View file
@@ -1,5 +1,5 @@
1.7.0rc1 (2016-11-18) 1.7rc1 (2016-11-18)
--------------------- -------------------


Compatibility Compatibility
~~~~~~~~~~~~~ ~~~~~~~~~~~~~
Expand All @@ -10,17 +10,18 @@ Compatibility
Backwards Incompatibility Backwards Incompatibility
~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~


- Response.set_cookie no longer accepts a key argument. This was deprecated in - ``Response.set_cookie`` no longer accepts a key argument. This was deprecated
WebOb 1.5 and as mentioned in the deprecation, is being removed in 1.7 in WebOb 1.5 and as mentioned in the deprecation, is being removed in 1.7


- Response `__init__` will no longer set the default Content-Type, nor - ``Response.__init__`` will no longer set the default Content-Type, nor
Content-Length on Responses that don't have a body. This allows WebOb to Content-Length on Responses that don't have a body. This allows WebOb to
return proper responses for things like `Response(status='204 No Content')`. return proper responses for things like `Response(status='204 No Content')`.


- Response.text will no longer raise if the Content-Type does not have a - ``Response.text`` will no longer raise if the Content-Type does not have a
charset, it will fall back to using the new default_body_encoding. To get the charset, it will fall back to using the new ``default_body_encoding`. To get
old behaviour back please sub-class Response and set default_body_encoding to the old behaviour back please sub-class ``Response`` and set
None. See https://github.com/Pylons/webob/pull/287 ``default_body_encoding`` to ``None``. See
https://github.com/Pylons/webob/pull/287


- WebOb no longer supports Chunked Encoding, this means that if you are using - WebOb no longer supports Chunked Encoding, this means that if you are using
WebOb and need Chunked Encoding you will be required to have a proxy that WebOb and need Chunked Encoding you will be required to have a proxy that
Expand All @@ -30,81 +31,77 @@ Backwards Incompatibility
Feature Feature
~~~~~~~ ~~~~~~~


- Response has a new default_body_encoding which may be used to allow - ``Response`` has a new ``default_body_encoding`` which may be used to allow
getting/setting Response.text when a Content-Type has no charset. See getting/setting ``Response.text`` when a Content-Type has no charset. See
https://github.com/Pylons/webob/pull/287 https://github.com/Pylons/webob/pull/287


- webob.Request with any HTTP method is now allowed to have a body. This allows - ``webob.Request`` with any HTTP method is now allowed to have a body. This
DELETE to have a request body for passing extra information. See allows DELETE to have a request body for passing extra information. See
https://github.com/Pylons/webob/pull/283 and https://github.com/Pylons/webob/pull/283 and
https://github.com/Pylons/webob/pull/274 https://github.com/Pylons/webob/pull/274


- Add `tell()` to `ResponseBodyFile` so that it may be used for example for - Add ``tell()`` to ``ResponseBodyFile`` so that it may be used for example for
ZipFile support. See https://github.com/Pylons/webob/pull/117 zipfile support. See https://github.com/Pylons/webob/pull/117


- Allow the return from `wsgify.middleware` to be used as a decorator. See - Allow the return from ``wsgify.middleware`` to be used as a decorator. See
https://github.com/Pylons/webob/pull/228 https://github.com/Pylons/webob/pull/228


Bugfix Bugfix
~~~~~~ ~~~~~~


- Fixup cgi.FieldStorage on Python 3.x to work-around issue reported in Python - Fixup ``cgi.FieldStorage`` on Python 3.x to work-around issue reported in
bug report 27777 and 24764. This is currently applied for Python versions Python bug report 27777 and 24764. This is currently applied for Python
less than 3.7. See https://github.com/Pylons/webob/pull/294 versions less than 3.7. See https://github.com/Pylons/webob/pull/294


- Response.set_cookie now accepts datetime objects for the expire kwarg and - ``Response.set_cookie`` now accepts ``datetime`` objects for the ``expires``
will correctly convert them to UTC with no tzinfo for use in calculating the kwarg and will correctly convert them to UTC with no tzinfo for use in
max_age. See https://github.com/Pylons/webob/issues/254 and calculating the ``max_age``. See https://github.com/Pylons/webob/issues/254
https://github.com/Pylons/webob/pull/292 and https://github.com/Pylons/webob/pull/292


- Fixes request.PATH_SAFE to contain all of the path safe characters according - Fixes ``request.PATH_SAFE`` to contain all of the path safe characters
to RFC3986. See https://github.com/Pylons/webob/pull/291 according to RFC3986. See https://github.com/Pylons/webob/pull/291


- WebOb's exceptions will lazily read underlying variables when inserted into - WebOb's exceptions will lazily read underlying variables when inserted into
templates to avoid expensive computations/crashes when inserting into the templates to avoid expensive computations/crashes when inserting into the
template. This had a bad performance regression on Py27 because of the way template. This had a bad performance regression on Py27 because of the way
the lazified class was created and returned. See the lazified class was created and returned. See
https://github.com/Pylons/webob/pull/284 https://github.com/Pylons/webob/pull/284


- `wsgify.__call__` raised a `TypeError` with an unhelpful message, it will now - ``wsgify.__call__`` raised a ``TypeError`` with an unhelpful message, it will
return the `repr` for the wrapped function: now return the ``repr`` for the wrapped function:
https://github.com/Pylons/webob/issues/119 https://github.com/Pylons/webob/issues/119


- Response.content_type removes the charset content_type parameters unless the - ``Response.content_type`` removes the charset content-type parameter unless
new content_type is a text like type that has a charset parameter. the new content-type is a text like type that has a charset parameter. See
See https://github.com/Pylons/webob/pull/261 and https://github.com/Pylons/webob/pull/261 and
https://github.com/Pylons/webob/issues/130 https://github.com/Pylons/webob/issues/130


- Response.json's json.dumps/loads are now always UTF-8. It no longer tries to - ``Response.json``'s ``json.dumps``/``json.loads`` are now always UTF-8. It no
use the charset. longer tries to use the charset.

- Response `__init__` will no longer set the default Content-Type, nor
Content-Length on Responses that don't have a body. This allows WebOb to
return proper responses for things like `Response(status='204 No Content')`.


- The Response `__init__` will by default no longer set the Content-Type to the - The ``Response.__init__`` will by default no longer set the Content-Type to
default if a headerlist is provided. This fixes issues whereby the default if a ``headerlist`` is provided. This fixes issues whereby
`Request.get_response()` would return a Response that didn't match the actual ``Request.get_response()`` would return a Response that didn't match the
response. actual response. See https://github.com/Pylons/webob/pull/261 and
See https://github.com/Pylons/webob/pull/261 and
https://github.com/Pylons/webob/issues/205 https://github.com/Pylons/webob/issues/205


- Cleans up the remainder of the issues with the updated WebOb exceptions that - Cleans up the remainder of the issues with the updated WebOb exceptions that
were taught to return JSON in version 1.6. See were taught to return JSON in version 1.6. See
https://github.com/Pylons/webob/issues/237 and https://github.com/Pylons/webob/issues/237 and
https://github.com/Pylons/webob/issues/236 https://github.com/Pylons/webob/issues/236


- Response.from_file now parses the status line correctly when the status line - ``Response.from_file`` now parses the status line correctly when the status
contains an HTTP with version, as well as a status text that contains line contains an HTTP with version, as well as a status text that contains
multiple white spaces (e.g HTTP/1.1 404 Not Found). See multiple white spaces (e.g HTTP/1.1 404 Not Found). See
https://github.com/Pylons/webob/issues/250 https://github.com/Pylons/webob/issues/250


- Response now has a new property named `has_body` that may be used to - ``Response`` now has a new property named ``has_body`` that may be used to
interrogate the Response to find out if `Response.body` is or isn't set. interrogate the ``Response`` to find out if ``Response.body`` is or isn't
set.


This is used in the exception handling code so that if you use a WebOb HTTP This is used in the exception handling code so that if you use a WebOb HTTP
Exception and pass a generator to `app_iter` WebOb won't attempt to read the Exception and pass a generator to ``app_iter`` WebOb won't attempt to read
whole thing and instead allows it to be returned to the WSGI server. See the whole thing and instead allows it to be returned to the WSGI server. See
https://github.com/Pylons/webob/pull/259 https://github.com/Pylons/webob/pull/259


1.6.0 (2016-03-15) 1.6.0 (2016-03-15)
Expand Down

0 comments on commit bc024c8

Please sign in to comment.