Author smurfix
Recipients smurfix
Date 2018-02-15.14:02:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1518703352.66.0.467229070634.issue32850@psf.upfronthosting.co.za>
In-reply-to
Content
Lib/test/support/__init__.py::threading_cleanup() complains about dangling threads even if the reference in question would be cleaned up by the garbage collector.

This is not useful, esp. when the list of referrers to the "dangling" thread looks like this:

[<frame at 0x7fe830195768, file '/usr/lib/python3.7/threading.py', line 869, code run>, <frame at 0x7fe828000b38, file '/usr/lib/python3.7/threading.py', line 966, code _bootstrap_inner>, <frame at 0x7fe83018aac8, file '/usr/lib/python3.7/threading.py', line 889, code _bootstrap>]

Thus I propose to check, run gc, check again, and only *then* complain-and-wait. Hence the attached patch for your consideration.
History
Date User Action Args
2018-02-15 14:02:32smurfixsetrecipients: + smurfix
2018-02-15 14:02:32smurfixsetmessageid: <1518703352.66.0.467229070634.issue32850@psf.upfronthosting.co.za>
2018-02-15 14:02:32smurfixlinkissue32850 messages
2018-02-15 14:02:32smurfixcreate