Better error message for "unprintable TypeError object"

[Ursula Junque]

Recently I've seen oopses like OOPS-1658EB4331:
  TypeError: <unprintable TypeError object>

This error is really unhelpful. We'd need more information about the context of that error in order to be able to debug it.

<gary_poster> ... for instance, if the code here gets a type error, we raise something with a better rendering of the account object (using removeSecurityProxy? Dunno).

[Michael Nelson (noodles775+sca-test-deactivatedaccount)]

These oopses are related to a change I landed last week :/ See bug 598464 which I've marked as QA bad.

[Ursula Junque (ursinha)]

In my opinion this is another problem. Not the oopses themselves, but the fact that the error message says nothing about the problem. I guess the real dupe of 598464 is 607479.

[Ursula Junque (ursinha)]

or bug 607479