➜

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 pitrou
Recipients CyberJacob, Decorater, Matt Groth, ellisj, eric.araujo, lazka, mwh, ncoghlan, pitrou, serhiy.storchaka, tiagoaoa, tim.peters, undercoveridiot, vlasovskikh, vstinner
Date 2019-05-25.21:11:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558818713.5.0.145340492229.issue1230540@roundup.psfhosted.org>
In-reply-to
Content 
Sorry, I had overlooked the issue with global variables at shutdown.  Though that issue only occurs with daemonic threads, since non-daemonic threads are joined before global variables are cleared.

In any case, I think the namedtuple / structseq solution is elegant, because we can add additional information later (the user must only be careful not to use tuple unpacking).
History
Date User Action Args
2019-05-25 21:11:53pitrousetrecipients: + pitrou, mwh, tim.peters, ncoghlan, ellisj, vstinner, tiagoaoa, eric.araujo, undercoveridiot, vlasovskikh, serhiy.storchaka, lazka, Decorater, CyberJacob, Matt Groth
2019-05-25 21:11:53pitrousetmessageid: <1558818713.5.0.145340492229.issue1230540@roundup.psfhosted.org>
2019-05-25 21:11:53pitroulinkissue1230540 messages
2019-05-25 21:11:53pitroucreate