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, byrnes, eric.snow, lukasz.langa, matrixise, ncoghlan, serhiy.storchaka, superluser, twouters
Date 2016-02-02.23:22:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If you're affected, there's a workaround. Use the following script to rewrite paths in your .zip file to be zipimport-compatible:

It preserves the preamble and all file metadata.

A little context why this is useful: for archives that are effectively "static" environments with entire dependency trees in them, this bug causes both a big slowdown in startup time (counted in seconds), as well as tens of megabytes of .pyc created on the fly. Examples include zipapp-style .pyz, Twitter's .pex or Facebook's .par. 

So while we're waiting for a new zipimport implementation, the workaround listed above should unblock people uzing this form of Python package distribution.
Date User Action Args
2016-02-02 23:22:51lukasz.langasetrecipients: + lukasz.langa, twouters, brett.cannon, ncoghlan, eric.snow, serhiy.storchaka, matrixise, superluser, byrnes
2016-02-02 23:22:51lukasz.langasetmessageid: <>
2016-02-02 23:22:51lukasz.langalinkissue25710 messages
2016-02-02 23:22:51lukasz.langacreate