python-WebOb-1.7.4-1.11

- Drop not needed python-pytest-cov BuildRequires

- update to 1.7.4:
- Add support for `wsgi.input_terminated` in the wsgi environ to allow for
  Chunked Encoding to be used with WebOb

- update to 1.7.3:
  - Request.host_url, Request.host_port and Request.domain now all understand and
    know how to parse IPv6 Host headers sent by browsers. See
    https://github.com/Pylons/webob/pull/332

- Fix Provides/Obsoletes.

- update to 1.7.2:
  - Allow unnamed fields in form data to be properly transcoded when calling
    request.decode with an alternate encoding. See
    https://github.com/Pylons/webob/pull/309
- Switch to singlespec approach

- 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

- update to 1.6.2:
  * 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

- fix download url

- update to 1.6.1:
  - 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 404 Not Found). See
    https://github.com/Pylons/webob/issues/250
  - Python 3.2 is no longer supported by WebOb
  - Request.decode attempted to read from the an already consumed stream, it has
    now been redirected to another stream to read from. See
    https://github.com/Pylons/webob/pull/183
  - The application/json media type does not allow for a charset as discovery of
    the encoding is done at the JSON layer. Upon initialization of a Response
    WebOb will no longer add a charset if the content-type is set to JSON. See
    https://github.com/Pylons/webob/pull/197 and
    https://github.com/Pylons/pyramid/issues/1611
  - Lazily HTML escapes environment keys in HTTP Exceptions so that those keys in
    the environ that are not used in the output of the page don't raise an
    exception due to inability to be properly escaped. See
    https://github.com/Pylons/webob/pull/139
  - MIMEAccept now accepts comparisons against wildcards, this allows one to
    match on just the media type or sub-type, without having to explicitly match
    on both the media type and sub-type at the same time. See
    https://github.com/Pylons/webob/pull/185
  - Add the ability to return a JSON body from an exception. Using the Accept
    information in the request, the exceptions will now automatically return a
    JSON version of the exception instead of just HTML or text. See
    https://github.com/Pylons/webob/pull/230 and
    https://github.com/Pylons/webob/issues/209
  - exc._HTTPMove and any subclasses will now raise a ValueError if the location
    field contains a line feed or carriage return. These values may lead to
    possible HTTP Response Splitting. The header_getter descriptor has also been
    modified to no longer accept headers with a line feed or carriage return.
    See: https://github.com/Pylons/webob/pull/229 and
    https://github.com/Pylons/webob/issues/217

- updateto version 1.5.1:
  * (Bug Fixes) The exceptions HTTPNotAcceptable,
    HTTPUnsupportedMediaType and HTTPNotImplemented will now correctly
    use the sub-classed template rather than the default error
    template. See https://github.com/Pylons/webob/issues/221
  * (Bug Fixes) Response?s from_file now correctly deals with a status
    line that contains an HTTP version identifier. HTTP/1.1 200 OK is
    now correctly parsed, whereas before this would raise an error
    upon setting the Response.status in from_file. See
    https://github.com/Pylons/webob/issues/121
- 1.5.0
  * (Bug Fixes) The cookie API functions will now make sure that
    max_age is an integer or an string that can convert to an
    integer. Previously passing in max_age=?test? would have silently
    done the wrong thing.
- 1.5.0b0
  * (Bug Fixes) Unbreak req.POST when the request method is
    PATCH. Instead of returning something cmpletely unrelated we
    return NoVar. See: https://github.com/Pylons/webob/pull/215
  * (Features) HTTP Status Code 308 is now supported as a Permanent
    Redirect. See https://github.com/Pylons/webob/pull/207
- 1.5.0a1
  * (Backwards Incompatibilities) Response.set_cookie renamed the only
    required parameter from ?key? to ?name?. The code will now still
    accept ?key? as a keyword argument, and will issue a
    DeprecationWarning until WebOb 1.7.
  * (Backwards Incompatibilities) The status attribute of a Response
    object no longer takes a string like None None and allows that to
    be set as the status. It now has to at least match the pattern of
    <integer status code> <explenation of status code>. Invalid status
    strings will now raise a ValueError.
- 1.5.0a0
  * (Backwards Incompatibilities) Morsel will no longer accept a
    cookie value that does not meet RFC6265?s cookie-octet
    specification. Upon calling Morsel.serialize a warning will be
    issued, in the future this will raise a ValueError, please update
    your cookie handling code. See
    https://github.com/Pylons/webob/pull/172
  * (Backwards Incompatibilities) Response.set_cookie now uses the
    internal make_cookie API, which will issue warnings if cookies are
    set with invalid bytes. See
    https://github.com/Pylons/webob/pull/172
  * (Features) Add support for some new caching headers,
    stale-while-revalidate and stale-if-error that can be used by
    reverse proxies to cache stale responses temporarily if the
    backend disappears. From RFC5861. See
    https://github.com/Pylons/webob/pull/189
  * (Bug Fixes) Response.status now uses duck-typing for integers, and
    has also learned to raise a ValueError if the status isn?t an
    integer followed by a space, and then the reason. See
    https://github.com/Pylons/webob/pull/191
  * (Bug Fixes) Fixed a bug in webob.multidict.GetDict which resulted
    in the QUERY_STRING not being updated when changes were made to
    query params using Request.GET.extend().
  * (Bug Fixes) Read the body of a request if we think it might have a
    body. This fixes PATCH to support bodies. See
    https://github.com/Pylons/webob/pull/184
  * (Bug Fixes) Response.from_file returns HTTP headers as latin1
    rather than UTF-8, this fixes the usage on Google AppEngine. See
    https://github.com/Pylons/webob/issues/99 and
    https://github.com/Pylons/webob/pull/150
  * (Bug Fixes) Fix a bug in parsing the auth parameters that
    contained bad white space. This makes the parsing fall in line
    with what?s required in RFC7235. See
    https://github.com/Pylons/webob/issues/158
  * (Bug Fixes) Use ?rn? line endings in Response.__str__. See:
    https://github.com/Pylons/webob/pull/146
  * (Documentation Changes) response.set_cookie now has proper
    documentation for max_age and expires. The code has also been
    refactored to use cookies.make_cookie instead of duplicating the
    code. This fixes https://github.com/Pylons/webob/issues/166 and
    https://github.com/Pylons/webob/issues/171
  * (Documentation Changes) Documentation didn?t match the actual code
    for the wsgify function signature. See
    https://github.com/Pylons/webob/pull/167
  * (Documentation Changes) Remove the WebDAV only from certain HTTP
    Exceptions, these exceptions may also be used by REST services for
    example.