Skip to content

Conversation

@rickeylev
Copy link
Collaborator

@rickeylev rickeylev commented Jan 25, 2026

This adds Python zipapp support as a separate rule that works with a py_binary.

This will eventually replace the zipapp logic that is directly part of py_binary.

The high level behavior should be the same, but there's a few differences and improvements:

Changes:

  • Output name is {name}.pyz
  • Whether the output is executable is controlled by attribute, not flag.

Improvements:

  • Compression level can be explicitly controlled.
  • Re-unzipping optimization: only unzip if the zip's hash changed
  • Zip output is more deterministic (input order doesn't affect output)
  • runfiles.symlinks, runfiles.root_symlinks, and raw symlinks are supported
  • Zipping venv-based binary is supported
  • Lower analysis-phase cost
  • Self-execution doesn't require python itself

For now, this lacks Windows support for lack of time (it requires plumbing in the
"windows exe maker" stuff or equivalent for self-executable zip support).

Along the way:

  • Add PyExecToolsInfo.exec_runtime: an easier way to get the RBE-compatible runtime
  • Add PyExecutableInfo fields to aid packaging a binary.
  • Set --verbose_failures in CI config to give more info when actions fail.
  • Make --visible_for_testing a command line flag. This makes it a bit easier to
    debug toolchain issues by showing the source of the toolchain.
  • Add actions_run helper: this makes it easier to use py scripts as build actions.

Work towards #3324 #2586

@rickeylev rickeylev requested a review from aignas as a code owner January 25, 2026 00:41
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @rickeylev, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a comprehensive overhaul of Python zip application (zipapp) support within the Bazel rules. By extracting zipapp creation into new, dedicated py_zipapp_binary and py_zipapp_test rules, the change aims to provide a more robust, feature-rich, and performant mechanism for packaging Python applications. It enhances control over the build process, improves determinism, and lays the groundwork for future advancements in Python binary distribution.

Highlights

  • New Zipapp Rules Introduced: Dedicated py_zipapp_binary and py_zipapp_test rules have been added to replace the existing zipapp logic within py_binary and py_test. These new rules offer enhanced functionality and improved build performance.
  • Improved Zipapp Features: The new zipapp rules provide explicit control over compression levels, optimize re-unzipping by checking the zip's hash, ensure more deterministic zip output, and support various symlink types (runfiles.symlinks, runfiles.root_symlinks, and raw symlinks). They also support zipping venv-based binaries.
  • Output and Executability: Generated zipapps now have a .pyz extension, and their executability is controlled via a dedicated attribute rather than a flag, offering more granular control.
  • Refactored Internal Logic: Significant internal refactoring has occurred, including the introduction of maybe_create_repo_mapping and actions_run functions in common.bzl, and a more detailed PyExecutableInfo provider to support the new zipapp structure and its various components like app_runfiles and stage2_bootstrap.
  • New Tools and Templates: New Python scripts (zipper.py, exe_zip_maker.py) and shell/Python templates (zip_shell_template.sh, zipapp_stage2_bootstrap_template.py) have been added to facilitate the creation and execution of these advanced zipapps.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a significant new feature: dedicated rules for creating Python zipapps (py_zipapp_binary and py_zipapp_test). This is a substantial refactoring that moves zipapp creation logic out of the generic py_binary rule, improving modularity and adding features like explicit compression control and enhanced determinism. The changes are extensive, touching many parts of the Python rules, including common utilities, executable creation, and providers. The new tooling for zipping and creating executables is well-designed and thoroughly tested.

Overall, the implementation is of high quality. However, I've identified a couple of critical issues in the new macros that would lead to build failures due to missing imports. I've also found a logic bug in a shell script template that affects a debugging feature. I've provided suggestions to fix these issues. The rest of the changes, including the refactoring of runfiles handling and the new actions_run helper, are excellent improvements.

@rickeylev
Copy link
Collaborator Author

@gemini-code-assist review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces py_zipapp_binary and py_zipapp_test rules, a significant enhancement for Python zipapp support that will eventually replace the existing logic within py_binary. The changes are extensive, refactoring core py_executable logic to expose more details for packaging, adding new tools for zip creation, and including a comprehensive set of tests. The implementation is well-structured, with new logic cleanly organized into a new zipapp package. I've identified a couple of potential issues with argument handling that could cause build failures in certain edge cases, but overall, this is an excellent and valuable addition to rules_python.

@rickeylev
Copy link
Collaborator Author

OK, ready for review. PTAL

Copy link
Collaborator

@aignas aignas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general LGTM. Thank you for easy to read code!

return "rf-file|" + _is_symlink(file) + "|" + file.short_path + "|" + file.path

def _map_zip_symlinks(entry):
return "rf-symlink|" + _is_symlink(entry.target_file) + "|" + entry.path + "|" + entry.target_file.path
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I remember that "%s" % "foo" being faster than "{}".format. Is + even better to use than "%s" or are they equivalent?

def _create_self_executable_zip(ctx, preamble, zip_file):
pyz = ctx.actions.declare_file(ctx.label.name + ".pyz")
args = ctx.actions.args()
args.add(preamble)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: why not use add_all?


py_zipapp_binary = rule(
doc = """
Packages a `py_binary` as a Python zipapp.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +57 to +61
exec_runtime = (
ctx.toolchains["@rules_python//python:exec_tools_toolchain_type"].
exec_tools.exec_interpreter[platform_common.ToolchainInfo].py3_runtime
)
```
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great addition!


# NOTE: Using ctx.actions.symlink() here doesn't always work with RBE
# because it's not guaranteed that it will materialize as a symlink, but
# we rely on it being a symlink so that Python can find its actual
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does this mean to me as a maintainer. Do some RBE implementation not work with our code? Does it not work sometimes? Do we have the RBE support for this disabled because of this?

@@ -0,0 +1,40 @@
import hashlib
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this private to the zipapp? I would personally have it in python/private/zipapp/exe_zip_maker.py until somebody comes along and asks for this to be exposed.

@@ -0,0 +1,230 @@
import argparse
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

that are associated with the target's `srcs` are present.
([#3354](https://github.com/bazel-contrib/rules_python/issues/3354)).
* (zipapp) {obj}`py_zipapp_binary` and {obj}`py_zipapp_test` rules added. These
will replace `--build_python_zip` and the zip output group of
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when do you want to replace these? Next major version? Should we add some deprecation messages?

py_zipapp_binary(
name = "system_python_zipapp",
binary = ":system_python_bin",
target_compatible_with = NOT_WINDOWS,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about windows and zipapps? If I understand correctly, Windows most of the time is building zips under the hood?

It would be good to have a comment somewhere about plans/strategy of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants