This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients ezio.melotti, michael.foord, pitrou
Date 2013-03-23.22:06:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After the subtests commit (5c09e1c57200/#16997), test_queue started showing the following warning:
Warning -- threading._dangling was modified by test_queue
1 test altered the execution environment:

The warning was caused by the fact that the TestCase subclasses in test_queue kept references to the thread, but before 5c09e1c57200 these subclasses (and hence the references to the thread) were destroyed before the regrtest check for threading._dangling, whereas now they are kept alive (due to Lib/unittest/, that adds a reference to the TestCase even in case of success).  I now fixed the warning in test_queue (1747e50fca55), however unittest should probably avoid keeping alive TestCases when they are not needed anymore.

See also #9815.

(Thanks to Antoine for the help while I was debugging the issue.)
Date User Action Args
2013-03-23 22:06:48ezio.melottisetrecipients: + ezio.melotti, pitrou, michael.foord
2013-03-23 22:06:48ezio.melottisetmessageid: <>
2013-03-23 22:06:48ezio.melottilinkissue17534 messages
2013-03-23 22:06:48ezio.melotticreate