|author||Jon Brandvein <firstname.lastname@example.org>||Tue May 14 15:59:21 2019 -0400|
|committer||GitHub <email@example.com>||Tue May 14 15:59:21 2019 -0400|
Add note on bazel version compatibility to WORKSPACE (#107) This will be useful to keep up-to-date for documentation purposes, and so we know when a release cut breaks compatibility with Bazel and therefore needs to be a major release.
Subpar is a utility for creating self-contained python executables. It is designed to work well with Bazel.
git_repository( name = "subpar", remote = "https://github.com/google/subpar", tag = "1.0.0", )
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.
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
This is not an official Google product, it is just code that happens to be owned by Google.