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 brett.cannon
Recipients
Date 2005-01-06.07:19:06
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=357491

What does Semaphore have to do with _DummyThread and 
currentThread?

And as for win32api, that is not part of the Python stdlib and thus I have 
no way of commenting on that.

For C++ threads to call into Python code, I would not say that is bad 
specifically.  You were just trying to get thread info for non-Python 
threads and that was leading to _DummyThread instances to be created 
as designed and you just didn't want that.  Calling Python code is fine, 
just don't expect it to know about your C++ threads as much as you 
seem to want it to.

And please leave this bug closed.  If free to submit a patch to change 
semantics, but that does not affect this bug report.
History
Date User Action Args
2007-08-23 14:28:38adminlinkissue1089632 messages
2007-08-23 14:28:38admincreate