Patches item #1680978, was opened at 2007-03-14 21:21 Message generated for change (Comment added) made by sonderblade You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1680978&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: None Status: Closed Resolution: Accepted Priority: 5 Private: No Submitted By: Bj�rn Lindqvist (sonderblade) Assigned to: Nobody/Anonymous (nobody) Summary: Use "alive" instead of "active" in the docs for threading Initial Comment: The documentation for the threading module uses the words "alive" and "active" interchangeably for describing a thread whose start() method has been called, but whose run() method has not finished. This patch intends to make the docs a little clearer by only using the "alive" word. The patch fixes Bug #912943 and is supposed to obsolete Patch #1107656 (which changes "alive" -> "active" and deprecates Thread.isAlive()). ---------------------------------------------------------------------- >Comment By: Bj�rn Lindqvist (sonderblade) Date: 2007-03-15 10:58 Message: Logged In: YES user_id=51702 Originator: YES Thansk. Don't forget to close Patch #1107656. ---------------------------------------------------------------------- Comment By: Georg Brandl (gbrandl) Date: 2007-03-15 08:38 Message: Logged In: YES user_id=849994 Originator: NO Thanks for the patch, committed in rev. 54392, 54393 (2.5). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1680978&group_id=5470
_______________________________________________ Patches mailing list Patches@python.org http://mail.python.org/mailman/listinfo/patches
