[issue26869] unittest longMessage docs

2016-10-13 Thread Guido van Rossum
Guido van Rossum added the comment: Done. Thanks! -- nosy: +gvanrossum resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue26869] unittest longMessage docs

2016-10-13 Thread Roundup Robot
Roundup Robot added the comment: New changeset 7eb4fe57492f by Guido van Rossum in branch '3.5': Issue #26869: Document unittest.TestCase.longMessage. (Mariatta) https://hg.python.org/cpython/rev/7eb4fe57492f New changeset d7279d803d1d by Guido van Rossum in branch '3.6': Issue #26869: Document

[issue26869] unittest longMessage docs

2016-10-10 Thread Thomas Guettler
Thomas Guettler added the comment: @Mariatta thank you very much. This update makes the docs easy to read and understand. Thank you :-) -- ___ Python tracker

[issue26869] unittest longMessage docs

2016-10-04 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: Hi, please review the updated documentation. Thanks. -- keywords: +patch Added file: http://bugs.python.org/file44965/issue26869.patch ___ Python tracker

[issue26869] unittest longMessage docs

2016-09-28 Thread Mariatta Wijaya
Changes by Mariatta Wijaya : -- nosy: +Mariatta ___ Python tracker ___ ___

[issue26869] unittest longMessage docs

2016-09-27 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +berker.peksag versions: +Python 3.7 ___ Python tracker ___

[issue26869] unittest longMessage docs

2016-04-28 Thread Thomas Guettler
Thomas Guettler added the comment: Thank you for understanding my concern. > The standard failure message for each *assert method* contains useful > information about the objects involved. For example the message from > assertEqual shows the repr of the two unequal objects. It is usually

[issue26869] unittest longMessage docs

2016-04-27 Thread Terry J. Reedy
Terry J. Reedy added the comment: Replace existing description with "This class attribute determines what happens when a custom failure message is passed as the msg argument to an assertXYY call that fails. If True, the default, the custom message is appended to the end of the standard

[issue26869] unittest longMessage docs

2016-04-27 Thread Thomas Guettler
New submission from Thomas Guettler: The first message of the longMessage docs is confusing: https://docs.python.org/3/library/unittest.html#unittest.TestCase.longMessage > If set to True then This reads between the lines, that the default is False. But that was long ago in Python2. In