[Patches] [ python-Patches-1739468 ] Add a -z interpreter flag to execute a zip file
noreply at sourceforge.net
Tue Jun 19 13:21:07 CEST 2007
Patches item #1739468, was opened at 2007-06-19 13:40
Message generated for change (Comment added) made by ncoghlan
You can respond by visiting:
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core (C code)
Submitted By: andy-chu (andy-chu)
>Assigned to: Nick Coghlan (ncoghlan)
Summary: Add a -z interpreter flag to execute a zip file
The motivation for this is that distributing a zip file is a very light and easy way to distribute a python program with multiple packages/modules. I have done this on Linux, Mac and Windows and it works very nicely -- except that you need a few extra files to bootstrap it: set PYTHONPATH to the zip file and run the main function.
With this small patch, you get rid of the need for extra files. At the bottom is a demo on Linux.
On Windows, you can do a similar thing by making a file that is both a zip file and a batch file. The batch file will pass %~f0 (itself) to the -z flag of the Python interpreter.
I ran this by Guido and he seemed to think it was a fine idea. At Google, we have numerous platform-specific hacks in a program called "autopar" to solve this problem.
I have included the basic patch, but if you guys agree with this, I will add some tests and documentation. And I think it might be useful to include something in the Tools/ directory to do what update_zip.sh does below (add a __zipmain__ module and a shebang/batch file header to a zip file, to make it executable)?
I think this may also help to fix a bug with eggs:
IMPORTANT NOTE: Eggs with an "eggsecutable" header cannot be renamed, or invoked via symlinks. They must be invoked using their original filename, in order to ensure that, once running, pkg_resources will know what project and version is in use. The header script will check this and exit with an error if the .egg file has been renamed or is invoked via a symlink that changes its base name.
andychu testdata$ ls
__zipmain__.py foo.py foo.pyc foo.zip foo_exe.zip header.txt update_zip.sh
# The main program you're going to run in "development mode"
andychu testdata$ ./foo.py foo bar
argv: ['./foo.py', 'foo', 'bar']
# Same program, packaged into a zip file
andychu testdata$ ./foo_exe.zip foo bar
argv: ['-c', 'foo', 'bar']
# Contents of the zip file
andychu testdata$ unzip -l foo_exe.zip
warning [foo_exe.zip]: 51 extra bytes at beginning or within zipfile
(attempting to process anyway)
Length Date Time Name
-------- ---- ---- ----
243 06-18-07 20:01 __zipmain__.py
301 06-18-07 19:58 foo.py
544 2 files
# Demo script to build an executable zip file.
andychu testdata$ cat header.txt
andychu testdata$ cat update_zip.sh
# Make a regular zip file.
zip foo.zip foo.py __zipmain__.py
# Add a shebang line to it.
cat header.txt foo.zip > foo_exe.zip
# Make it executable.
chmod 750 foo_exe.zip
>Comment By: Nick Coghlan (ncoghlan)
Date: 2007-06-19 21:21
Logged In: YES
I like the general idea, but it should be possible to use runpy.run_module
to get __name__ set correctly (as that is what happens when you execute a
module from a zipfile with -m). Another advantage of using run_module is
that it would allow runzip() to take a second argument (possibly defaulting
to "__zipmain__") which would specify the module to be executed from the
zipfile (the remaining 3 run_module arguments could also be passed in, and
set appropriately from main.c).
Adding the new function as runpy.run_zip() (instead of adding a new
module) would also be good.
For Windows, an alternative to making the zip file both a batch and a zip
file would be to adopt a .pyz extension convention for these files - the
file associations can then be set up to invoke the script appropriately
with python -z (similar to the way that .pyw files are associated with
pythonw instead of the standard python executable). That way the same file
could be executed on both Linux (via an embedded shebang line) and on
Windows (via filename association), as is the case with standard .py Python
My final question is whether the change to sys.path should be reverted
once the module execution is complete - my suspicion is that it should, but
I need to look into it a bit more before giving a definite answer (for the
command line flag case, this behaviour obviously doesn't matter - it is
only significant if the Python method is invoked directly in the context of
a larger program).
You can respond by visiting:
More information about the Patches