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 brett.cannon
Recipients brett.cannon, brian.curtin, nadeem.vawda, pitrou, rhettinger, serhiy.storchaka
Date 2013-01-21.18:00:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358791253.18.0.728872232406.issue17004@psf.upfronthosting.co.za>
In-reply-to
Content
So this seems like a confluence of both supporting compressed files for loading source code as well as supporting new archive formats (e.g. xz vs. tar); zip just happens to do both implicitly. And there is also the question of if you explicitly plan to do this in C code or in pure Python as I plan to introduce a pure Python version of zipimport into importlib for 3.4 so that it can use zipfile directly and thus all of its full support of zipfile abilities.

And there doesn't have to be any performance cost in trying to write bytecode files; it's very simple to have a loader which simply skips that step entirely.
History
Date User Action Args
2013-01-21 18:00:53brett.cannonsetrecipients: + brett.cannon, rhettinger, pitrou, nadeem.vawda, brian.curtin, serhiy.storchaka
2013-01-21 18:00:53brett.cannonsetmessageid: <1358791253.18.0.728872232406.issue17004@psf.upfronthosting.co.za>
2013-01-21 18:00:53brett.cannonlinkissue17004 messages
2013-01-21 18:00:52brett.cannoncreate