)]}'
{
  "commit": "7a1b10c4eb2a01084298537fae46f60ecf97cb6c",
  "tree": "f65eea8dbd90529aaf9e99e41b7a3517f391849f",
  "parents": [
    "ab0cc82b343ad93736ea4094844839a717190fd8"
  ],
  "author": {
    "name": "Serge Bazanski",
    "email": "serge@nexantic.com",
    "time": "Tue Feb 11 10:02:21 2020 +0100"
  },
  "committer": {
    "name": "Serge Bazanski",
    "email": "serge@nexantic.com",
    "time": "Tue Feb 11 10:02:21 2020 +0100"
  },
  "message": "Explicitly provide Python toolchain, provide `python` in build container\n\nThis fixes being able to run py_binary targets within the build\ncontainer.\n\nEach py_binary creates a stub that always has the #!/usr/bin/env python\nshebang, and as such we need to have `python` available in the build\ncontainer. The stub then dispatches into the right Python interpreter,\nwhich we now configure explicitely via rules_python\u0027s py_runtime_pair.\n\nTest Plan: nothing breaks, future uses of py_binary (eg D389) will make actual use of this\n\nX-Origin-Diff: phab/D390\nGitOrigin-RevId: 78b6c51f09c720a46fbe2e6cbadb2a97d1161f7b\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "99080be408f2bc7082876868178b001f8b082bd6",
      "old_mode": 33188,
      "old_path": "BUILD",
      "new_id": "29fce8d38995fcbf82dbeb7b809fa3d2f99c376a",
      "new_mode": 33188,
      "new_path": "BUILD"
    },
    {
      "type": "modify",
      "old_id": "62796fb2eb9c53ec6389d30d59eab92fef582f0f",
      "old_mode": 33188,
      "old_path": "WORKSPACE",
      "new_id": "3f3598a64cff2c8b465b0ce2c55bf0ff51af835c",
      "new_mode": 33188,
      "new_path": "WORKSPACE"
    },
    {
      "type": "modify",
      "old_id": "e07e60d5c89bf99c33b80635a4fe9c9a41d3f16d",
      "old_mode": 33188,
      "old_path": "build/Dockerfile",
      "new_id": "7332d90547c4981d34d3fd537a85aa0b4510d01f",
      "new_mode": 33188,
      "new_path": "build/Dockerfile"
    }
  ]
}