Some changes in the way errors from Omeka are handled:
- Omeka responses with HTTP status codes in the 400s and 500s will now generate exceptions rather than return nothing or some unexpected JSON. This should make for more consistent handling of responses, and easier bug checking.
- If Omeka has returned something that can't be parsed as JSON, the raw response text will be displayed (to help with debugging) and a JSONDecodeException will be raised
I think the only major impact will be in calls to get_resource_by_id() which previously returned None if the resource didn't exist. A non-existent resource will now generate an HTTPError triggered by a 404 status code.