[issue1163] Patch to make py3k/Lib/test/test_thread.py use unittest

Brett Cannon <[EMAIL PROTECTED]> added the comment: Closing as out of date as a GHOP attempt at this got farther and committed. -- nosy: +brett.cannon resolution: -> out of date status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue1163] Patch to make py3k/Lib/test/test_thread.py use unittest

Changes by Sean Reifschneider: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue1163] Patch to make py3k/Lib/test/test_thread.py use unittest

Guido van Rossum added the comment: This is a good start, but I think that instead of using global variables and functions, you should try to turn all those into instance variables (of the ThreadTest class). That way the tests are truly independent. Initialization should be taken care of in set

[issue1163] Patch to make py3k/Lib/test/test_thread.py use unittest

Changes by Martin v. Löwis: -- keywords: +patch __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue1163] Patch to make py3k/Lib/test/test_thread.py use unittest

New submission from Jono DiCarlo: In the google spreadsheet for py3k tasks for the sprint last month, one of the listed tasks was to convert Lib/test/test_thread to use the unittest module, where it previously was using the old-style testing (i.e. comparing output of print statements to a text fi