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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, henrietta, pitrou, vstinner
Date 2011-01-19.17:48:42
SpamBayes Score 0.0036989104
Marked as misclassified No
Message-id <1295459338.1.0.968910846848.issue10923@psf.upfronthosting.co.za>
In-reply-to
Content
> "import child_directory"
Then it's certainly an effect of the "import lock":
http://docs.python.org/library/threading.html#importing-in-threaded-code

In your case, the first call to encode('utf8') indirectly imports utf8.py, while the import lock is held by 'import child_directory'.
Then the self.loglock is the second resource that closes the deadlock loop.

A workaround is to add some call to encode('utf8') before the thread is created.
History
Date User Action Args
2011-01-19 17:48:58amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, pitrou, vstinner, henrietta
2011-01-19 17:48:58amaury.forgeotdarcsetmessageid: <1295459338.1.0.968910846848.issue10923@psf.upfronthosting.co.za>
2011-01-19 17:48:42amaury.forgeotdarclinkissue10923 messages
2011-01-19 17:48:42amaury.forgeotdarccreate