Skip to content
/ subpar Public
forked from google/subpar

Subpar is a utility for creating self-contained python executables. It is designed to work well with Bazel.

License

Notifications You must be signed in to change notification settings

jo2y/subpar

This branch is 12 commits behind google/subpar:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

a4f9b23 · Dec 19, 2018

History

83 Commits
Nov 15, 2017
Dec 19, 2018
Dec 15, 2017
Feb 12, 2018
Oct 12, 2016
Nov 9, 2017
Apr 10, 2018
Nov 13, 2017
Nov 9, 2017
Dec 15, 2017
Dec 15, 2017
Aug 3, 2016
Aug 3, 2016
Aug 3, 2016
Oct 31, 2017
Nov 9, 2017
Aug 3, 2016
Aug 3, 2016
Jan 29, 2018
Apr 17, 2018
Nov 27, 2018
Sep 19, 2017

Repository files navigation

Subpar

Build Status

Subpar is a utility for creating self-contained python executables. It is designed to work well with Bazel.

Setup

  • Add the following to your WORKSPACE file:
git_repository(
    name = "subpar",
    remote = "https://github.com/google/subpar",
    tag = "1.0.0",
)
  • Add the following to the top of any BUILD files that declare par_binary() rules:
load("@subpar//:subpar.bzl", "par_binary")

Usage

par_binary() is a drop-in replacement for py_binary() in your BUILD files that also builds a self-contained, single-file executable for the application, with a .par file extension.

To build the .par file associated with a par_binary(name=myname) rule, do

bazel build //my/package:myname.par

The .par file is created alongside the python stub and .runfiles directories that py_binary() creates, but is independent of them. It can be copied to other directories or machines, and executed directly without needing the .runfiles directory. The body of the .par file contains all the srcs, deps, and data files listed.

Limitations:

  • C extension modules in 'deps' is not yet supported
  • Automatic re-extraction of '.runfiles' is not yet supported
  • Does not include a copy of the Python interpreter ('hermetic .par')

Example

Given a BUILD file with the following:

load("@subpar//:subpar.bzl", "par_binary")

par_binary(
    name = 'foo',
    srcs = ['foo.py', 'bar.py'],
    deps = ['//baz:some_py_lib'],
    data = ['quux.dat'],
)

Run the following build command:

bazel build //package:foo.par

This results in the following files being created by bazel build:

bazel-bin/
    package/
        foo
        foo.par
        foo.runfiles/
            ...

The .par file can be copied, moved, or renamed, and still run like a compiled executable file:

$ scp bazel-bin/package/foo.par my-other-machine:foo.par
$ ssh my-other-machine ./foo.par

System Requirements

  • Python Versions: CPython versions 2.7.6+
  • Operating Systems: Debian-derived Linux, including Ubuntu and Goobuntu.

DISCLAIMER

This is not an official Google product, it is just code that happens to be owned by Google.

About

Subpar is a utility for creating self-contained python executables. It is designed to work well with Bazel.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 93.9%
  • Shell 5.3%
  • Dockerfile 0.8%