assertRaises used as a method can't take a msg keyword argument because all args and keywords are passed to the callable.  But in context manager form it could, and this can be useful.  See, for example, issue 3583.

I'm fine with this functionality being added in 3.3.

I decided to try my hand at writing a patch for python.

I ended up implementing the behavior for assertRaises, assertRaisesRegex, assertWarns, and assertWarnsRegex. I also made those functions complain about other arguments rather then just ignoring them.

Changing callableObj to callable_obj in assertRaises will break for anyone that's upgrading to 3.3.  I left a comment on the review.

Aren't such use cases already covered by assertRaisesRegex?

How does assertRaisesRegex address the use case in issue 3583?

robquad mentions having left a comment on the review, but I'm not seeing how to view it. Can somebody explain?

It wasn't necessary to change the callable_obj bit, but both form were being used so I thought it best to standardize. Neither version of the parameter name shows up in the documentation.

Michael pointed out that I had completely missed the point of what the "msg" argument was about. Sorry for the noise.

> I left a comment on the review.
You need to publish your comment if you want others to see it.

I showed robquad how to do the review stuff at PyCon but I forgot about the publish part. Robbie, if you hit "Publish + Mail Comments" near the top of the page after you've left comments, it'll send them out.


What he noticed was that changing to callable_obj in the assertRaises signature could break anyone who had been using callableObj as a named argument. Although it isn't explicitly documented, it's a named argument that someone is probably using. As for standardizing, it's probably best to match the general format of the library which is camelCase, and change the internal uses rather than a public method signature.

The public methods were using both callable_obj and callableObj. Perhaps the patch should standardize on callableObj and accept callable_obj with a warning?

Attached a revised patch.
While I agree that an error should be raised when extra args are provided in the context manager form, this is out of the scope of the issue, so I didn't include those changes.

New patch by Ezio looks good to me. Go ahead and commit. Please raise a separate issue for error reporting when invalid argument combinations are used. (i.e. additional keyword arguments but no callable.)

New changeset 8fc801ca9ea1 by Ezio Melotti in branch 'default':
Issue #10775: assertRaises, assertRaisesRegex, assertWarns, and assertWarnsRegex now accept a keyword argument 'msg' when used as context managers.  Initial patch by Winston Ewert.
http://hg.python.org/cpython/rev/8fc801ca9ea1

Done, thanks for the patch!