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 barry
Recipients barry, brett.cannon, eric.snow, gvanrossum, lukasz.langa, ncoghlan, paul.moore, serhiy.storchaka, steve.dower, tim.golden, twouters, vstinner, zach.ware
Date 2018-04-03.20:14:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522786458.13.0.467229070634.issue30891@psf.upfronthosting.co.za>
In-reply-to
Content
Take a look at https://bugs.python.org/issue25711 which wants to rewrite zipimport from scratch.  I took Serhiy's C->Python patch and turned it into a PR, but it would need a lot of love to get it into shape.

(Let's not even talk about https://bugs.python.org/issue32866 which caused me some pain during importlib.resources work.)

Pretty sure Thomas's rumored rewrite is still in C, and it solves problems like support for zip64 and comments, which we've run into also.

zipimport is crucial for single-file executable solutions like pex and our own soon-to-be-open-sourced tool, so it really can't go away.  Both of those still unpack wheels/eggs/sdists to a file system cache, not so much for speed but because shared libraries generally can't be imported from anything but a physical path (thanks to dlopen()).  I think Google has a patch for glibc that would solve that but there's some hesitation from the glibc maintainers to merge it (and then what about other platforms?).
History
Date User Action Args
2018-04-03 20:14:18barrysetrecipients: + barry, gvanrossum, twouters, brett.cannon, paul.moore, ncoghlan, vstinner, tim.golden, lukasz.langa, eric.snow, zach.ware, serhiy.storchaka, steve.dower
2018-04-03 20:14:18barrysetmessageid: <1522786458.13.0.467229070634.issue30891@psf.upfronthosting.co.za>
2018-04-03 20:14:18barrylinkissue30891 messages
2018-04-03 20:14:18barrycreate