[issue1626] threading.Thread objects are not reusable after join()

/ reusability of the peer System Thread that will be used to effectively host the code execution)BR nbsp;BR Regards,BR nbsp;BR SebastienBRBRBRBR HR id=stopSpelling BR gt; Subject: [issue1626] threading.Thread objects are not reusable after join()BRgt; To: [EMAIL PROTECTED]BRgt; From: [EMAIL

[issue1626] threading.Thread objects are not reusable after join()

New submission from Sebastien BRACQUEMONT: After a call to join() method on a Threading.thread object,there is no way to successfully call start() method on it. Indeed, the __started flag is not reset in the theading.Thread join() method. Since the start() method checks for __started flag ,

[issue1626] threading.Thread objects are not reusable after join()

Amaury Forgeot d'Arc added the comment: From the documentation: http://docs.python.org/dev/library/threading.html#threading.Thread.start start() must be called at most once per thread object. I think this will not change: when a system thread terminates, you cannot restart it; you have to

[issue1626] threading.Thread objects are not reusable after join()

Martin v. Löwis added the comment: I agree with Amaury. This all works exactly as it should work, and will not change. -- nosy: +loewis __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1626 __