)]}'
{
  "commit": "1198422c8986c10af8e9313b2570e8a4dd2dc2b1",
  "tree": "cfb7f02787c1a857a4af7e254b1c82abc987a400",
  "parents": [
    "4558ffb0c6f97044dc2fb9731454a4797e549fcf"
  ],
  "author": {
    "name": "Richard Levasseur",
    "email": "richardlev@gmail.com",
    "time": "Sun Dec 14 15:27:50 2025 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sun Dec 14 23:27:50 2025 +0000"
  },
  "message": "refactor: optimize venv building for namespace packages (#3454)\n\nWhen implicit namespace packages are used, it\u0027s common for multiple\ndistributions\nto install into the same directory, triggering the expensive conflict\nmerging\nlogic. This can be observed wit our doc builds, where `sphinxcontrib` is\na\nnamespace package that 7 distributions install into.\n\nTo fix, treat top-level directories that have an importable name and\ndon\u0027t have an\n`__init__` looking file as implicit namespace packages and mark them as\ndisallowed\nfrom being directly linked. The importable name check is to exclude\ndist-info\ndirectories.\n\n---------\n\nCo-authored-by: gemini-code-assist[bot] \u003c176961590+gemini-code-assist[bot]@users.noreply.github.com\u003e",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0c79ea82a1ccf408f7929dabe95c6bac96a4a496",
      "old_mode": 33188,
      "old_path": "python/private/venv_runfiles.bzl",
      "new_id": "7ff5c8512c84ddfd0ff0abd879e36d731d114057",
      "new_mode": 33188,
      "new_path": "python/private/venv_runfiles.bzl"
    },
    {
      "type": "modify",
      "old_id": "486293b38dab0d48abc867a7e6f455ab84a56f1e",
      "old_mode": 33188,
      "old_path": "tests/venv_site_packages_libs/app_files_building/app_files_building_tests.bzl",
      "new_id": "e92c0aaf5a046331ec548a1e2050a8ff62c76a2b",
      "new_mode": 33188,
      "new_path": "tests/venv_site_packages_libs/app_files_building/app_files_building_tests.bzl"
    }
  ]
}