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 Rhamphoryncus, amaury.forgeotdarc, brett.cannon, brian.curtin, bronger, cwalther, gregory.p.smith, pitrou
Date 2010-03-29.14:50:41
SpamBayes Score 8.214099e-10
Marked as misclassified No
Message-id <1269874244.56.0.156282180376.issue1596321@psf.upfronthosting.co.za>
In-reply-to
Content
I think the fix to Christian's issue is just:

Index: Lib/threading.py
===================================================================
--- Lib/threading.py	(révision 79470)
+++ Lib/threading.py	(copie de travail)
@@ -579,7 +579,7 @@
                 try:
                     # We don't call self.__delete() because it also
                     # grabs _active_limbo_lock.
-                    del _active[_get_ident()]
+                    del _active[self.__ident]
                 except:
                     pass
 
@@ -615,7 +615,7 @@
 
         try:
             with _active_limbo_lock:
-                del _active[_get_ident()]
+                del _active[self.__ident]
                 # There must not be any python code between the previous line
                 # and after the lock is released.  Otherwise a tracing function
                 # could try to acquire the lock again in the same thread, (in


Now we just need to add a test for it in test_threading.
And, yes, Amaury's test case looks like a different issue.
History
Date User Action Args
2010-03-29 14:50:44pitrousetrecipients: + pitrou, brett.cannon, gregory.p.smith, amaury.forgeotdarc, Rhamphoryncus, bronger, cwalther, brian.curtin
2010-03-29 14:50:44pitrousetmessageid: <1269874244.56.0.156282180376.issue1596321@psf.upfronthosting.co.za>
2010-03-29 14:50:42pitroulinkissue1596321 messages
2010-03-29 14:50:41pitroucreate