Message259446
| 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 |
<1454455371.18.0.219318962151.issue25710@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
If you're affected, there's a workaround. Use the following script to rewrite paths in your .zip file to be zipimport-compatible:
https://gist.github.com/ambv/909d38bdac4f3e719b7c
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. |
|