Google Git
Sign in
fuchsia / third_party / github.com / google / subpar / refs/heads/upstream/dependabot/pip/tests/setuptools-65.5.1
commitfd4a3986acb609235f523652f741c2e3ddc71ada[log] [tgz]
authordependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>Tue Dec 27 14:53:52 2022 +0000
committerGitHub <noreply@github.com>Tue Dec 27 14:53:52 2022 +0000
treee8f87120cb5a0d748652e8bf7aa966d0d7c78c2d
parent5c486705da7fece4739015ce566423a8fd89916f [diff]
Bump setuptools from 5.5.1 to 65.5.1 in /tests

Bumps [setuptools](https://github.com/pypa/setuptools) from 5.5.1 to 65.5.1.
- [Release notes](https://github.com/pypa/setuptools/releases)
- [Changelog](https://github.com/pypa/setuptools/blob/main/CHANGES.rst)
- [Commits](https://github.com/pypa/setuptools/compare/5.5.1...v65.5.1)

---
updated-dependencies:
- dependency-name: setuptools
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
2 files changed
tree: e8f87120cb5a0d748652e8bf7aa966d0d7c78c2d
  1. .ci/
  2. compiler/
  3. docs/
  4. runtime/
  5. scripts/
  6. test_dir_shadowing/
  7. tests/
  8. third_party/
  9. .bazelrc
  10. .flake8
  11. .gitignore
  12. .travis.yml
  13. __init__.py
  14. BUILD
  15. CODEOWNERS
  16. CONTRIBUTING.md
  17. debug.bzl
  18. LICENSE
  19. nox.py
  20. README.md
  21. run_tests.sh
  22. subpar.bzl
  23. toolchain_test_hook.bzl
  24. update_docs.sh
  25. WORKSPACE
README.md

Subpar (deprecated)

Build Status

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

Status

This project is unmaintained and considered deprecated. Historically, subpar was the only way to produce a deployable Python artifact in Bazel. This is no longer true; --build_python_zip and the python_zip_file output_group allows you to create executable Python zip artifacts with the standard py_binary rule. rules_docker can also be used to build container images that launch py_binary.

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.