zipapps 2021.3.2

Package your python code into one zip file, even a virtual environment.

zipapps

Package your python code (with requirements) into a standalone zip file (like a jar).

zipapps is a pure-python library, without any 3rd-party dependencies. Inspired by shiv but unlike shiv, this lib will not always create new cache folders while running, and easy to combine multiple venv.pyz files then let them work well together.

What is the .pyz?

.pyz to Python is like .jar to Java. They are both zip archive files which aggregate many packages and associated metadata and resources (text, images, etc.) into one file for distribution. Then what you only need is a Python Interpreter as the runtime environment.

PS: The pyz ext could be any other suffixes even without ext names, so you can rename app.pyz to app.zip as you wish. Depends on PEP441, then the apps may be cross-platform as long as written with pure python code without any C++ building processes.

When to Use it?

1. Package your code(package or model) into one zipped file.
   1. sometimes togather with the requirements.
2. Run with python interpreter from venv
   1. which means the requirements(need to be unzipped) will be installed to the venv folder, not in pyz file.
   2. build your package into one pyz file with -m package.module:function -p /venv/bin/python.
   3. run the pyz file with /venv/bin/python app.pyz or ./app.pyz.
3. Hadoop-Streaming's mapper & reducer scripts.
4. Simple deployment towards different servers with jenkins, or other CI/CD tools.
   1. Easy to uploads a clean standalone zip file.
5. Distribute zipapp with embedded python.
6. Use as a requirements zip path, or some venv usages.
   1. import sys;sys.path.insert(0, 'app.pyz') (without .so/.pyd)
   2. python3 app.pyz script.py
7. Other usages need to be found, and enjoy yourself.

Install & Quick Start

pip install zipapps -U

zip as apps

1. zipapps with requirements

   1. python3 -m zipapps -u AUTO -a entry.py -m entry:main -o app.pyz aiohttp,psutils

2. run app.pyz

   1. python3 app.pyz

   2. libs with .pyd/.so caches will be unzipped to the ./zipapps_cache/app

zip as virtual environments

1. zipapps with requirements

   1. python3 -m zipapps -u AUTO -o venv.pyz -r requirements.txt

2. run entry.py with venv.pyz

   1. python3 venv.pyz entry.py

   2. cache will be unzipped to ./zipapps_cache/venv if -u is not null

How to Use?

Advance Usage

1. Package your script file with only built-ins functions.

1.1 Code of script.py

print('ok')

1.2 build the app.pyz

python3 -m zipapps -c -a script.py -m script -p /usr/bin/python3

1.3 run this app

python3 app.pyz

or

./app.pyz

ouput

ok

Details:

-c:
    compress files, 7.6KB => 3.3KB
-a:
    add the script file to app.pyz, so you can use it while running
-m:
    set the entry_point, also can be set as `-m script:main` as long as you has the main function
-p:
    set the shebang line, so you can use `./app.pyz` instead of `python3 app.pyz`

2. Package your package folder into one zip file.

2.1 The package example and the code of __main__.py

└── example
    ├── __init__.py
    └── __main__.py

def main():
    print('ok')


if __name__ == "__main__":
    main()

2.2 build the example.pyz

python3 -m zipapps -c -a example -o example.pyz -m example.main:main -p /usr/bin/python3

2.3 Run with python3 example.pyz or ./example.pyz

output

ok

Details:

-m:
    set the entry_point with format like `package.model:function`
-o:
    set the output file path, you can set it some other paths like `/home/centos/example.abc` and run with `python3 /home/centos/example.abc`
no more new args.

3. Package your code with requirements (bottle).

3.1 The package example and the code of __main__.py

    └── example
        ├── __init__.py
        └── __main__.py

def main():
    import bottle
    print(bottle.__version__)


if __name__ == "__main__":
    main()

3.2 build the example.pyz with requirements installed

python3 -m zipapps -c -a example -o example.pyz -m example.main:main bottle

3.3 Run with python3 example.pyz or ./example.pyz

Output

0.12.19

Details:

bottle:
    all the unhandled args like `bottle` will be used to `pip install`, so you can write `bottle` in requirements.txt and use like `-r requirements.txt`

WARNING: if the requirements have .pyd/.so files, you should unzip them while running, and the pure python libs like bottle or requests no need to unzip anything. Read the 4th paragraph for more info.

4. Package your code with the requirements which includes .pyd/.so files.

4.1 The package example and the code of __main__.py

└── example
    ├── __init__.py
    └── __main__.py

def main():
    import psutil
    print(psutil.__version__)


if __name__ == "__main__":
    main()

4.2 build the example.pyz with requirements installed

python3 -m zipapps -c -a example -o example.pyz -m example.main:main -u AUTO -up TEMP/cache psutil

4.3 Run with python3 example.pyz or ./example.pyz

Output

5.8.0

Details:

-u:
    means the file or folder names you want to unzip while running. Here is the `AUTO`, will unzip the psutil package because of its .pyd or .so files included.
-up:
    the unzip path of cache folder. TEMP / HOME / SELF are the built-in runtime args, but for the stable usage you can ignore this arg then use `./zipapps_cache/example`. The cache will be refreshed while you rebuild this pyz.

WARNING: unzip path can be overwrited by export ZIPAPPS_CACHE=./xxx or export UNZIP_PATH=./xxx while running.

5. Package the requirements like a virtual environment without entry_point.

5.1 Code of script.py

import bottle, requests
print(bottle.__version__, requests.__version__)

5.2 build the venv.pyz

python3 -m zipapps -c -o venv.pyz -p /usr/bin/python3 bottle requests

5.3.1 use the venv.pyz like a middleware

python3 venv.pyz script.py

5.3.2 use the venv.pyz like the interpreter

./venv.pyz script.py

even like is also valid

python3 venv.pyz -c "import bottle,requests;print(bottle.__version__, requests.__version__)"

Output

0.12.19 2.25.1

Details:

No `-m` arg here, then the pyz file will do like an interpreter which contains the installed requirements.

So you can use it like this:
> python3 venv.pyz
>>> import bottle
>>> bottle.__file__

6. Using multiple venv pyz files for your pyz model.

6.1 Here is script.py again

import bottle, requests
print(bottle.__version__, requests.__version__)

6.2 Build the script.pyz

python3 -m zipapps -c -o script.pyz -a script.py -m script requests

6.3 Build the requests.pyz and bottle.pyz respectively

python3 -m zipapps -c -o requests.pyz requests

python3 -m zipapps -c -o bottle.pyz bottle

6.4 And now run the script.pyz with two requirements

python3 script.pyz --zipapps=bottle.pyz,requests.pyz

Output

0.12.19 2.25.1

Details:

--zipapps:
    This arg will help you run some zipapp with given venv.pyz files, the paths is separated by commas.

Command line args

Packaging args

most common args:

• -c
  • to compress files, only for python3.7+.
• -a xxx.py
  • to add some files/folders into the zipped file.
• -u=AUTO
  • auto unzip the .pyd / .so files
• -r requirements.txt
  • install requirements with pip install
• -o my_app.pyz
  • output the zipped file as given path
• -m app.__main__:main
  • set the entry point
• -p /usr/bin/python3
  • set the shebang line

Details:

1. -h, --help
   1. show the simple doc
2. --includes, --add, -a
   1. The given paths will be copied to cache_path while packaging, which can be used while running. The path strings will be splited by ",".
      1. such as my_package_dir,my_module.py,my_config.json
      2. often used for libs not from pypi or some special config files
   2. the output arg of zipapps.create_app
3. --output, -o
   1. The path of the output file, defaults to app.pyz.
   2. the output arg of zipapps.create_app
4. --python, -p
   1. The path of the Python interpreter which will be set as the shebang line, defaults to None.
      1. with shebang /usr/bin/python3 you can run app with ./app.pyz directly, no need for python3 app.pyz
   2. the interpreter arg of zipapps.create_app
5. --main, -m
   1. The entry point function of the application, the valid format is:
      1. package.module:function
      2. package.module
      3. module:function
      4. package
   2. the main arg of zipapps.create_app
   3. WARNING: If the --main arg is set, python3 app.pyz will not be able to used as venv like python3 app.pyz xxx.py
6. --compress, -c
   1. Boolean value, compress files with the deflate method or not.
   2. the compressed arg of zipapps.create_app
7. --unzip, -u
   1. The names which need to be unzipped while running, splited by "," without ext, such as bottle,aiohttp, or the complete path like bin/bottle.py,temp.py. For .so/.pyd files(which can not be loaded by zipimport), or packages with operations of static files.
      1. if unzip is set to "*", then will unzip all files and folders.
      2. if unzip is set to AUTO, then will add the .pyd and .so files automatically.
   2. the unzip arg of zipapps.create_app
8. --unzip-path, -up
   1. If unzip arg is not null, cache files will be unzipped to the given path while running. Defaults to zipapps_cache, support some internal variables as runtime args:
      1. TEMP/HOME/SELF as prefix, for example HOME/zipapps_cache
         1. TEMP means tempfile.gettempdir()
         2. HOME means Path.home()
         3. SELF means .pyz file path.
      2. And you can also overwrite it with environment variables:
         1. ZIPAPPS_CACHE or UNZIP_PATH
   2. the unzip_path arg of zipapps.create_app
9. -cc, --pyc, --compile, --compiled
   1. Compile .py to .pyc for fast import, but zipapp does not work unless you unzip it(so NOT very useful).
   2. the compiled arg of zipapps.create_app
10. --cache-path, --source-dir, -cp
11. The cache path of zipapps to store site-packages and includes files. If not set, will create and clean-up in TEMP dir automately.
12. the cache_path arg of zipapps.create_app
13. --shell, -s
    1. Only while main is not set, used for shell=True in subprocess.run.
       1. very rarely used, because extra sub-process is not welcome
    2. the shell arg of zipapps.create_app
14. --main-shell, -ss
    1. Only for main is not null, call main with subprocess.Popen: python -c "import a.b;a.b.c()". This is used for psutil ImportError of DLL load.
       1. very rarely used too
    2. the main_shell arg of zipapps.create_app
15. --strict-python-path, -spp
    1. Boolean value. Ignore global PYTHONPATH, only use zipapps_cache and app.pyz.
    2. the ignore_system_python_path arg of zipapps.create_app
16. -b, --build-id
    1. The string to skip duplicate builds, it can be the paths of files/folders which splited by ",", then the modify time will be used as build_id. If build_id contains *, will use glob function to get paths. For example, you can set requirements.txt as your build_id by python3 -m zipapps -b requirements.txt -r requirements.txt when you use pyz as venv.
       1. very rarely used too too
    2. the build_id arg of zipapps.create_app
17. all the other (or unknown) args will be used by "pip install"
    1. such as -r requirements.txt
    2. such as bottle aiohttp
    3. the pip_args arg of zipapps.create_app

Runtime args

available args while the .pyz is running

1. --zipapps
   1. including some other pyz into PYTHONPATH
   2. often be used as multiple venv combination
   3. for example
      1. building
         1. python3 -m zipapps -o six.pyz six
         2. python3 -m zipapps -o psutil.pyz -u AUTO psutil
         3. python3 -m zipapps -o bottle.pyz bottle
      2. run
         1. python3 six.pyz --zipapps=psutil.pyz,bottle.pyz -c "import psutil, bottle"

Changelogs

• 2021.03.02
  • fix auto-unzip nonsense folders while -u AUTO but no need to unzip any files
• 2021.01.29
  • fix packaging zipapps self
    • python3 -m zipapps -m zipapps.__main__:main -a zipapps -o zipapps.pyz
  • add zipapps.pyz to release page
• 2021.01.28
  • fix bug: run .py file with run_path missing sys.argv
    • python3 app.pyz xxx.py -a -b -c
• 2021.01.11
  • add --zipapps arg while building pyz files
    • to activate some venv pyz with given paths while running it
    • also support TEMP/HOME/SELF prefix, these internal variables are still runtime args.
• 2020.12.27
  • Combile multiple pyz files, do like this:
    • python3 -m zipapps -o six.pyz six
    • python3 -m zipapps -o psutil.pyz -u AUTO psutil
    • python3 six.pyz --zipapps=psutil.pyz -c "import six,psutil;print(six.file, psutil.file)"
• 2020.12.23
  • --unzip support auto-check by -u AUTO, alias for --unzip=AUTO_UNZIP
  • fix run_module bug while running ./app.pyz -m module
• 2020.12.21
  • now will not run a new subprocess in most cases.
    • using runpy.run_path and runpy.run_module
    • and using subprocess.run instead of subprocess.call
• 2020.12.13
  • --unzip support complete path
  • --unzip support auto-check by --unzip=AUTO_UNZIP
• 2020.11.23
  • add activate_zipapps to activate zipapps PYTHONPATH easily
• 2020.11.21
  • reset unzip_path as the parent folder to unzip files
    • so the cache path will be like ./zipapps_cache/app/ for app.pyz,
    • this is different from old versions.
  • add environment variable ZIPAPPS_CACHE for arg unzip_path
  • add environment variable ZIPAPPS_UNZIP for arg unzip

Old Docs