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 brett.cannon, davin, ncoghlan, palmer, sbt
Date 2015-02-13.06:37:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1423809479.87.0.806880056793.issue15914@psf.upfronthosting.co.za>
In-reply-to
Content
3.2 is in security-fix only mode, so nothing's going to change there.

For 3.3+, the per-module import lock design means the issue doesn't happen.

However, I wonder if there may be some now dead code relating to the global import lock that could be deleted.
History
Date User Action Args
2015-02-13 06:37:59ncoghlansetrecipients: + ncoghlan, brett.cannon, sbt, palmer, davin
2015-02-13 06:37:59ncoghlansetmessageid: <1423809479.87.0.806880056793.issue15914@psf.upfronthosting.co.za>
2015-02-13 06:37:59ncoghlanlinkissue15914 messages
2015-02-13 06:37:59ncoghlancreate