I do actually like the idea of a generic middleware that translates Python exceptions into HTTP ones. Perhaps that would make for readable code. I'll let others comment on that idea though. Although that decorator is in addons, the only real place that ever uses it is the mkt API. All the rest is crufty old code.

some ideas
- move that decorator into the mkt codebase, so it doesn't affect anything else
- cope in dispatch in mkt/api/base.py with mapping python errors into http errors, since this is tastypie api, something in `dispatch` might work, however i'd like to see something similar in django rest framework
- or just catch the Python error in the API, `PreparePayResource` and turn it into a HTTP error code

The decorator was originally written assuming lots of views would use it. Since then we've ended with exactly one API that uses it. Perhaps just doing something in the API would be best.