<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/python-novaclient.git/novaclient/tests/unit/test_exceptions.py, branch master</title>
<subtitle>opendev.org: openstack/python-novaclient.git
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-novaclient.git/'/>
<entry>
<title>Handle error response for webob&gt;=1.6.0</title>
<updated>2016-03-18T23:22:03+00:00</updated>
<author>
<name>Matt Riedemann</name>
<email>mriedem@us.ibm.com</email>
</author>
<published>2016-03-18T23:17:47+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/openstack/python-novaclient.git/commit/?id=fa377e7fca44e81247639efebd7cae5cb377e57e'/>
<id>fa377e7fca44e81247639efebd7cae5cb377e57e</id>
<content type='text'>
WebOb change https://github.com/Pylons/webob/pull/230 changed
the way in which the error response body is formatted such that
it's no longer a nested dict. So we have to handle both the
old convention of an error message key to the response body error
dict and the new way with just the error body dict.

This was reported upstream:

https://github.com/Pylons/webob/issues/235

But given this was apparently implemented as a long-overdue change
in WebOb the behavior is not likely to change.

Change-Id: If653a247d842786d2824b4b3a5c0cde1383ed7ab
Closes-Bug: #1559072
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
WebOb change https://github.com/Pylons/webob/pull/230 changed
the way in which the error response body is formatted such that
it's no longer a nested dict. So we have to handle both the
old convention of an error message key to the response body error
dict and the new way with just the error body dict.

This was reported upstream:

https://github.com/Pylons/webob/issues/235

But given this was apparently implemented as a long-overdue change
in WebOb the behavior is not likely to change.

Change-Id: If653a247d842786d2824b4b3a5c0cde1383ed7ab
Closes-Bug: #1559072
</pre>
</div>
</content>
</entry>
</feed>
