[issue683658] PyErr_Warn may cause import deadlock

Changes by Georg Brandl: -- status: pending -> closed Tracker <[EMAIL PROTECTED]> ___ Python-bugs-list mailing list Unsubscribe: h

[issue683658] PyErr_Warn may cause import deadlock

Changes by Georg Brandl: -- status: open -> pending Tracker <[EMAIL PROTECTED]> ___ Python-bugs-list mailing list Unsubscribe: htt

[issue683658] PyErr_Warn may cause import deadlock

Guido van Rossum added the comment: Let's close this unless there's a response from one of the original stakeholders within a week (i.e. by Jan 11 2008). -- keywords: +patch -64bit Tracker <[EMAIL PROTECTED]>

[issue683658] PyErr_Warn may cause import deadlock

Guido van Rossum added the comment: No, backporting that to 2.5 isn't an option; it introduces a new feature and breaks binary backwards compatibility by removing the PyImport_ImportModuleEx entry point from the executable (turning it into a macro). -- assignee: gvanrossum -> keywords:

[issue683658] PyErr_Warn may cause import deadlock

Christian Heimes added the comment: Is this still an issue for 2.5? If Python 2.5 may still dead lock then somebody should back port my PyImport_ImportModuleNoBlock() function. -- nosy: +tiran priority: normal -> high versions: +Python 2.5 -Python 2.3 ___