From 6485203cb593353418e7b486dd2a5a12fe0e609ddc143a15320f7129e954f730 Mon Sep 17 00:00:00 2001 From: Dirk Mueller Date: Tue, 4 Apr 2017 06:50:20 +0000 Subject: [PATCH] Accepting request 456072 from home:tbechtold:branches:devel:languages:python - update to 1.7.1: - ``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. See https://github.com/Pylons/webob/issues/305 - WebOb is no longer supported on Python 2.6 and PyPy3 (due to pip no longer supporting Python 3.2 even on PyPy) - ``Response.content_type`` removes all existing Content-Type parameters, and if the new Content-Type is "texty" it adds a new charset (unless already provided) using the ``default_charset``. See https://github.com/Pylons/webob/pull/301 - ``Response.set_cookie`` no longer accepts a key argument. This was deprecated 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 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')`. - ``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 old behaviour back please sub-class ``Response`` and set ``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 and need Chunked Encoding you will be required to have a proxy that unchunks the request for you. Please read https://github.com/Pylons/webob/issues/279 for more background. - ``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 OBS-URL: https://build.opensuse.org/request/show/456072 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-WebOb?expand=0&rev=37 --- WebOb-1.6.2.tar.gz | 3 -- WebOb-1.7.1.tar.gz | 3 ++ python-WebOb.changes | 83 ++++++++++++++++++++++++++++++++++++++++++++ python-WebOb.spec | 4 +-- 4 files changed, 88 insertions(+), 5 deletions(-) delete mode 100644 WebOb-1.6.2.tar.gz create mode 100644 WebOb-1.7.1.tar.gz diff --git a/WebOb-1.6.2.tar.gz b/WebOb-1.6.2.tar.gz deleted file mode 100644 index aefbe42..0000000 --- a/WebOb-1.6.2.tar.gz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e096c20ec672412f7d463fd5ed23f71b9176945c66b8adb8b781b8cda174de84 -size 205228 diff --git a/WebOb-1.7.1.tar.gz b/WebOb-1.7.1.tar.gz new file mode 100644 index 0000000..da19f41 --- /dev/null +++ b/WebOb-1.7.1.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b2e3e4a46ce92614fb7d85081a63d03fa0c714dbe0195d5d91ec0205526c83f +size 215517 diff --git a/python-WebOb.changes b/python-WebOb.changes index 75232ec..6f289a9 100644 --- a/python-WebOb.changes +++ b/python-WebOb.changes @@ -1,3 +1,86 @@ +------------------------------------------------------------------- +Fri Feb 10 16:14:42 UTC 2017 - tbechtold@suse.com + +- update to 1.7.1: + - ``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. See + https://github.com/Pylons/webob/issues/305 + - WebOb is no longer supported on Python 2.6 and PyPy3 (due to pip no longer + supporting Python 3.2 even on PyPy) + - ``Response.content_type`` removes all existing Content-Type parameters, and + if the new Content-Type is "texty" it adds a new charset (unless already + provided) using the ``default_charset``. See + https://github.com/Pylons/webob/pull/301 + - ``Response.set_cookie`` no longer accepts a key argument. This was deprecated + 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 + 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')`. + - ``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 old behaviour back please sub-class ``Response`` and set + ``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 and need Chunked Encoding you will be required to have a proxy that + unchunks the request for you. Please read + https://github.com/Pylons/webob/issues/279 for more background. + - ``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 + https://github.com/Pylons/webob/pull/287 + - ``webob.Request`` with any HTTP method is now allowed to have a body. This + 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/274 + - Add ``tell()`` to ``ResponseBodyFile`` so that it may be used for example for + zipfile support. See https://github.com/Pylons/webob/pull/117 + - Allow the return from ``wsgify.middleware`` to be used as a decorator. See + https://github.com/Pylons/webob/pull/228 + - Fixup ``cgi.FieldStorage`` on Python 3.x to work-around issue reported in + Python bug report 27777 and 24764. This is currently applied for Python + versions less than 3.7. See https://github.com/Pylons/webob/pull/294 and + https://github.com/Pylons/webob/pull/300 + - ``Response.set_cookie`` now accepts ``datetime`` objects for the ``expires`` + kwarg and will correctly convert them to UTC with no tzinfo for use in + calculating the ``max_age``. See https://github.com/Pylons/webob/issues/254 + and https://github.com/Pylons/webob/pull/292 + - Fixes ``request.PATH_SAFE`` to contain all of the path safe characters + according to RFC3986. See https://github.com/Pylons/webob/pull/291 + - WebOb's exceptions will lazily read underlying variables when inserted into + templates to avoid expensive computations/crashes when inserting into the + template. This had a bad performance regression on Py27 because of the way + the lazified class was created and returned. See + https://github.com/Pylons/webob/pull/284 + - ``wsgify.__call__`` raised a ``TypeError`` with an unhelpful message, it will + now return the ``repr`` for the wrapped function: + https://github.com/Pylons/webob/issues/119 + - ``Response.json``'s ``json.dumps``/``json.loads`` are now always UTF-8. It no + longer tries to use the charset. + - The ``Response.__init__`` will by default no longer set the Content-Type to + the default if a ``headerlist`` is provided. This fixes issues whereby + ``Request.get_response()`` would return a Response that didn't match the + actual response. See https://github.com/Pylons/webob/pull/261 and + https://github.com/Pylons/webob/issues/205 + - Cleans up the remainder of the issues with the updated WebOb exceptions that + were taught to return JSON in version 1.6. See + https://github.com/Pylons/webob/issues/237 and + https://github.com/Pylons/webob/issues/236 + - ``Response.from_file`` now parses the status line correctly when the status + 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 + https://github.com/Pylons/webob/issues/250 + - ``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. + 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 whole thing and instead allows it to be returned to the WSGI server. See + https://github.com/Pylons/webob/pull/259 + ------------------------------------------------------------------- Sat Oct 15 09:37:15 UTC 2016 - dmueller@suse.com diff --git a/python-WebOb.spec b/python-WebOb.spec index d8ed2bd..e9c8fb9 100644 --- a/python-WebOb.spec +++ b/python-WebOb.spec @@ -1,7 +1,7 @@ # # spec file for package python-WebOb # -# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2017 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -17,7 +17,7 @@ Name: python-WebOb -Version: 1.6.2 +Version: 1.7.1 Release: 0 Summary: WSGI request and response object License: MIT