➜
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.
Created on 2013-03-23 22:06 by ezio.melotti, last changed 2022-04-11 14:57 by admin.
| Messages (3) | |||
|---|---|---|---|
| msg185100 - (view) | Author: Ezio Melotti (ezio.melotti) *  |
Date: 2013-03-23 22:06 | |
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: test_queue 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/case.py:72, 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.) |
|||
| msg185195 - (view) | Author: Michael Foord (michael.foord) * |
Date: 2013-03-25 11:52 | |
Issue 11798 is somewhat related. |
|||
| msg331666 - (view) | Author: Serhiy Storchaka (serhiy.storchaka) * |
Date: 2018-12-11 23:25 | |
Does this issue still relevant? |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:43 | admin | set | status: pending -> open github: 61736 |
| 2018-12-11 23:25:10 | serhiy.storchaka | set | status: open -> pending nosy: + serhiy.storchaka messages: + msg331666 |
| 2013-10-06 20:01:45 | tshepang | set | nosy:
+ tshepang |
| 2013-10-06 19:31:00 | terry.reedy | set | versions: - Python 3.2 |
| 2013-03-25 11:52:44 | michael.foord | set | messages: + msg185195 |
| 2013-03-23 22:06:48 | ezio.melotti | create | |