| commit | 04f5798f7ad0827b33b8bd96d225820d4a91b0b2 | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Tue Jul 09 23:33:01 2024 -0700 |
| committer | GitHub <noreply@github.com> | Wed Jul 10 06:33:01 2024 +0000 |
| tree | 74f42524a62ab0dbfdd7a92513cc160bfe06a4aa | |
| parent | 1d0c9a78eeb1fdee29b52f62ff482d9e8a03c2be [diff] |
tests: add integration test for build_python_zip (#2045) This is a more comprehensive regression test for verifying `--build_python_zip` is actually working (https://github.com/bazelbuild/rules_python/issues/1840) This also creates a small framework to make it easier to write integration tests that need to customize the environment bazel runs in and check the output of bazel itself. I figure this will be helpful for writing simple verification tests for repository/bzlmod phase logic (i.e. set the debug env vars and grep the output). While we should avoid heavy usage of these bazel-in-bazel tests, a bit of grepping logs would go a long way for covering edge cases that examples don't cover.
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.