[issue25651] Confusing output for TestCase.subTest(0)

2017-03-31 Thread Donald Stufft
Changes by Donald Stufft : -- pull_requests: +1077 ___ Python tracker ___ ___

[issue25651] Confusing output for TestCase.subTest(0)

2016-09-21 Thread Berker Peksag
Berker Peksag added the comment: Fixed. I lost some time because of this today :) -- nosy: +berker.peksag resolution: -> fixed stage: test needed -> resolved status: open -> closed versions: +Python 3.7 -Python 3.4 ___ Python tracker

[issue25651] Confusing output for TestCase.subTest(0)

2016-09-21 Thread Roundup Robot
Roundup Robot added the comment: New changeset ba743894e793 by Berker Peksag in branch '3.5': Issue #25651: Allow falsy values to be used for msg parameter of subTest() https://hg.python.org/cpython/rev/ba743894e793 New changeset ddbf92168a44 by Berker Peksag in branch '3.6': Issue #25651:

[issue25651] Confusing output for TestCase.subTest(0)

2015-12-16 Thread Zachary Ware
Zachary Ware added the comment: I think Ezio's suggestion of a sentinel value would be better, allowing None to be using as a legitimate 'message' [1]. That is, somewhere at global scope, define '_subtest_msg_sentinel = object()', change the msg default at Lib/unittest/case.py:500 to be

[issue25651] Confusing output for TestCase.subTest(0)

2015-11-21 Thread Nan Wu
Nan Wu added the comment: Made it check against None explicitly. My concern is if [] is passed in, if will show [[]]. But this case should be rare. -- keywords: +patch nosy: +Nan Wu Added file: http://bugs.python.org/file41115/subtest_msg_check_against_None.patch

[issue25651] Confusing output for TestCase.subTest(0)

2015-11-17 Thread Ezio Melotti
New submission from Ezio Melotti: When a single positional argument is passed to subTest(), if the argument is false, its value won't be displayed in the output -- () will appear instead: >>> import unittest >>> class NumbersTest(unittest.TestCase): ... def test_odd(self): ... for i in