Case study: debugging failed assertRaises bug

[R David Murray]

Ben Finney <ben+python <at> benfinney.id.au> writes:
> > (1) assertRaises REALLY needs a better error message. If not a custom
> > message, at least it should show the result it got instead of an
> > exception.
> 
> +1
> 
> Is this one of the many improvements in Python 3.2's ‘unittest’ that
> Michael Foord presided over? Or are we still stuck with the terrible
> behaviour of ‘assertRaises’?

No, but issue 10775 [1] is just waiting for Michael (or someone else
who has time) to commit the patch.

--David

[1] http://bugs.python.org/issue10775