[Python-Dev] PEP 4XX: pyzaa "Improving Python ZIP Application Support"

Daniel Holth dholth at gmail.com
Mon Apr 8 05:01:13 CEST 2013

On Wed, Apr 3, 2013 at 1:26 AM, Stefan Behnel <stefan_ml at behnel.de> wrote:
> Brett Cannon, 02.04.2013 19:28:
>> On Tue, Apr 2, 2013 at 1:20 PM, Steve Dower <Steve.Dower at microsoft.com>wrote:
>>>> python -m pyzaa pack [-o path/name] [-m module.submodule:callable] [-c]
>>> [-w] [-p interpreter] directory:
>>>>    ZIP the contents of directory as directory.pyz or [-w]
>>> directory.pyzw. Adds the executable flag to the archive.
>>>> ...
>>>>    -p interpreter include #!interpreter as the first line of the archive
>>> What happens when -p is omitted? I'd hope it would add the interpreter
>>> used to create the zip (or at least the major version), but that may not be
>>> ideal for some reason that I haven't thought of yet.
>> Question is whether ``/usr/bin/python3.3`` is better or ``/usr/bin/env
>> python3.3``. I vote for the latter since it gets you the right thing
>> without having to care about whether the interpreter moved or is being
>> hidden by a user-installed interpreter.
> It can't work properly from within a virtualenv when you write
> "/usr/bin/python", so using "/usr/bin/env" instead is actually required.
> Stefan

Pushed as Draft PEP 441, tooling prototyped (with less than awesome
CLI) at https://bitbucket.org/dholth/pyzaa or


Daniel Holth

More information about the Python-Dev mailing list