initial commit: minimal repro of rules_python/issues/2283.

bazel-contrib/rules_python#2283.

Author: Ubehebe

.bazelrc

@@ -0,0 +1 @@
+common --incompatible_strict_action_env

.bazelversion

@@ -0,0 +1,18 @@
+load("@rules_python//python:defs.bzl", "py_binary")
+load("@rules_python//python:pip.bzl", "compile_pip_requirements")
+
+compile_pip_requirements(
+    name = "requirements",
+    requirements_in = "requirements.in",
+    requirements_txt = "requirements.txt",
+)
+
+py_binary(
+    name = "main",
+    srcs = [
+        "main.py",
+    ],
+    deps = [
+        "@pip//pandas:pkg",
+    ],
+)

BUILD

@@ -0,0 +1,29 @@
+module(
+    name = "rules_python_2283_mvce",
+)
+
+bazel_dep(
+    name = "rules_python",
+    version = "1.0.0",
+)
+
+python_version = "3.12.3"
+
+python = use_extension("@rules_python//python/extensions:python.bzl", "python")
+python.toolchain(
+    is_default = True,
+    python_version = python_version,
+)
+
+pip = use_extension("@rules_python//python/extensions:pip.bzl", "pip")
+
+# Install all python deps, using the python interpreter above.
+# For each package foo listed in requirements.txt, this creates a @pip_foo repo
+# with a top-level :pkg py_library target.
+pip.parse(
+    hub_name = "pip",
+    python_version = python_version,
+    quiet = False,
+    requirements_lock = ":requirements.txt",
+)
+use_repo(pip, "pip")

MODULE.bazel

@@ -0,0 +1,34 @@
+This repo demonstrates the python toolchain cache invalidation from
+https://github.com/bazelbuild/rules_python/issues/2283.
+
+## Overview
+The repo contains a trivial python script (`main.py`) that imports a package from pip.
+A python toolchain is configured using the latest versions of bazel (8.0.0) and rules_python
+(1.0.0).
+
+`pre-commit.sh` is a git pre-commit hook, used to abort a commit if any target fails to build.
+
+## Setup
+
+1. Clone the repo
+2. Symlink `pre-commit.sh` to `.git/hooks/pre-commit`
+3. `bazel build ...`
+4. Make a change to the repo that bazel won't notice (e.g. edit README.md). This is just to
+   convince git to run the pre-commit hook in the next step.
+5. `git commit -am "some message"`
+
+## Expected results
+
+The first build, in step 3, should print messages like this:
+
+```
+Collecting pandas==2.1.4 (from -r /var/folders/28/qqqxx4y55dz08x1bzcc9z7jm0000gn/T/tmpyann5bc8 (line 1))
+```
+
+The second build, called from the pre-commit hook in step 5, shouldn't print any of these messages,
+since the packages should already be cached.
+
+## Observed results
+
+The second build does print `Collecting pandas` messages, showing that the package cache is
+invalidated.

MODULE.bazel.lock

@@ -0,0 +1 @@
+8.0.0

README.md

@@ -0,0 +1,6 @@
+from pandas import DataFrame
+
+# This script doesn't do anything. i just needed a dependency on a pip package to exhibit
+# https://github.com/bazelbuild/rules_python/issues/2283.
+if __name__ == "__main__":
+    print(f"{DataFrame}")

bazelversion

@@ -0,0 +1,11 @@
+#!/usr/bin/env bash
+
+# pre-commit hook. ln -s this to .git/hooks/pre-commit.
+
+set -x
+
+# when this script is run as a git hook, git sets GIT_EXEC_PATH automatically.
+# when this script is run directly, this should not be set.
+env | grep GIT_EXEC_PATH
+
+bazel build ...

main.py

@@ -0,0 +1 @@
+pandas==2.1.4