Various assert methods added in version 2.7 ignore the longMessage attribute:http://docs.python.org/2.7/library/unittest.html#unittest.TestCase.longMessageFor example when matching regular expressions using unittest.TestCase.assertRegexpMatches, the following error is generated:AssertionError: <custom short message>: '<regexp>' not found in '<text>'Since longMessage is ignored, and the text to be matched can be pages long, the error messages are impossibly long.[See also:http://stackoverflow.com/questions/21157905/suppress-supplementary-error-message-from-unit-test]

I've added missing self._formatMessage() functions to assertRegex and assertNotRegex asserts.

This fix has been retested with 2.7, I'm uploading the relevant patch files.

Modified to work with 3.5. Attaching patch file.

Thanks for the patches, Ilia. The one for 2.7 looks good.Reviewing 20362_py35.patch:* Looks almost identical toissue20362.diff except style changes and the two comments below, right?* -            self.assertIn("'kot'", e.args[0])  Why did you remove this line?* +    assertNotRegexpMatches = _deprecate(assertNotRegex)  This looks like an unrelated change, but I think it can be committed. Thanks for the catch!* The tests should be updated to use assertRegex and assertNotRegex

Thanks for the quick response, Berker! Let me address your comments in the order you made them.#1: removing checking for "kot" in the exception args.This line was causing the tests to fail, which is how I noticed it. The reason it fails (I think) is caused by the changes made in the patch. Namely, the fact that we're strictly sticking to longMessage=False means the custom message passed by the user (in this particular case that's "Message") is be the *only* thing sent to AssertionError. Thus checking for the presence of "kot" in this error's args doesn't seem to make much sense and will simply keep breaking our tests.Now it goes without saying that I may have missed something, please let me know if that's the case.#2For some reason I got the impression that the tests should be using the newer method names, but since using the old ones didn't break them on my machine, I've updated the patch file accordingly. I'll upload it pending your feedback regarding #1.Glad to help!Ilia.

Hi Berker!I hope all's well on your end. Let me know if you have questions about the reasoning behind my changes.

Hi there!I was wondering if anyone had a chance to take a look at this :)

I notice folks have been subscribing to this. Any chance we could review it and merge? :)

* The removal of the 'kot' test is ok. That's what the fix is about. With longMessage set to False, we should only see the custom message, 'Message', and not the message about the regex that contains 'kot'.* Please update the patch for 3.5 to use assertRegex and assertNotRegex in the assertMessages call. These are the new names. With the current patch, the tests throw deprecation warnings.Other than that the patch looks good (I am not a committer, though, so I can't help further).

Sorry for my late response, Ilia. Your reply to my first question looks correct to me. Please send your updated patch and I'll apply.

Thanks for the feedback, folks. Adding the updated patch.

Bump :)Let's close this one, guys!

New changeset738de9a9a3ea by Robert Collins in branch '3.5':Issue#20362: Honour TestCase.longMessage correctly in assertRegex.https://hg.python.org/cpython/rev/738de9a9a3eaNew changeset977e60f597de by Robert Collins in branch 'default':Issue#20362: Honour TestCase.longMessage correctly in assertRegex.https://hg.python.org/cpython/rev/977e60f597de

Thanks for the patch, applied to 3.5 and 3.6.