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 lukasz.langa
Recipients brett.cannon, eric.snow, gvanrossum, lukasz.langa, ncoghlan, paul.moore, serhiy.storchaka, steve.dower, tim.golden, twouters, vstinner, zach.ware
Date 2018-04-02.17:46:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522691181.63.0.467229070634.issue30891@psf.upfronthosting.co.za>
In-reply-to
Content
In the context of this issue: zipimport doesn't properly lock on imports happening in multiple threads at the same time. This causes one thread to receive a partially imported module while the other thread is still performing the import.

zipimport also doesn't properly check __pycache__ directories but *does* look for old-style .pyc files next to the corresponding .py file.

IIRC Brett chooses not to deal with zipimport's warts and has no time to rewrite it in Python. Since the rest of the core team is less qualified, they steer clear, too.

So, don't use zipimport.
History
Date User Action Args
2018-04-02 17:46:21lukasz.langasetrecipients: + lukasz.langa, gvanrossum, twouters, brett.cannon, paul.moore, ncoghlan, vstinner, tim.golden, eric.snow, zach.ware, serhiy.storchaka, steve.dower
2018-04-02 17:46:21lukasz.langasetmessageid: <1522691181.63.0.467229070634.issue30891@psf.upfronthosting.co.za>
2018-04-02 17:46:21lukasz.langalinkissue30891 messages
2018-04-02 17:46:21lukasz.langacreate