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 grahamd
Recipients belopolsky, brett.cannon, christian.heimes, grahamd, gvanrossum, ncoghlan, pitrou
Date 2010-07-14.22:36:03
SpamBayes Score 0.0012198754
Marked as misclassified No
Message-id <>
How is this going to deal with cyclical imports where different threads could import at the same time different modules within that cycle? I need to look through the proposed patch and work out exactly what it does, but am concerned about whether this approach would cause the classic deadlock problem if not done right?

FWIW, this concept of a lock per module is what I used in the mod_python module importer when it was rewritten. I would have to go look back over that code and see how the way the concept is being implemented differs, but there was one remaining potential race condition in the mod_python code which could in rare instances cause a problem. I never did get around to fixing it. Anyway, what I did learn was that this approach isn't necessarily as simple as it may seem so it will need some really good analysis on whatever solution is developed to ensure subtle problems don't come up.
Date User Action Args
2010-07-14 22:36:09grahamdsetrecipients: + grahamd, gvanrossum, brett.cannon, ncoghlan, belopolsky, pitrou, christian.heimes
2010-07-14 22:36:09grahamdsetmessageid: <>
2010-07-14 22:36:04grahamdlinkissue9260 messages
2010-07-14 22:36:03grahamdcreate