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 ncoghlan
Recipients belopolsky, brett.cannon, christian.heimes, grahamd, ncoghlan
Date 2010-07-13.12:21:41
SpamBayes Score 9.75625e-05
Marked as misclassified No
Message-id <>
OK, finally tracked down some of the history here. Issue 1567 is the one where Christian developed the relevant patch which was then committed as r59678.

Issue 7980 is also potentially related (although that's apparently a Mac OS X crash involving time.strptime rather than an ImportError exception).

I think what it boils down to is that this approach to the import deadlock problem is far too pessimistic. If any other import is going on when an implicit import is triggered using this function makes the assumption that the other thread is going to be waiting for the current thread at some point, so this thread can't afford to wait for the import lock and should throw an exception instead. That's going to disallow a lot of perfectly legitimate imports, particularly when the Python interpreter is embedded in a multi-threaded application rather than running standalone.
Date User Action Args
2010-07-13 12:21:44ncoghlansetrecipients: + ncoghlan, brett.cannon, belopolsky, christian.heimes, grahamd
2010-07-13 12:21:44ncoghlansetmessageid: <>
2010-07-13 12:21:42ncoghlanlinkissue8098 messages
2010-07-13 12:21:41ncoghlancreate