)]}'
{
  "commit": "06672cd470ce513a256c7ef2dbb8497a0f5502f3",
  "tree": "639206f17688311c92a852f9f0c5686ad1f13971",
  "parents": [
    "e251c60348a54e5a0f361c9819a41fa46db2dfd1"
  ],
  "author": {
    "name": "Kevin Ku",
    "email": "kevin@akitasoftware.com",
    "time": "Tue Jun 23 22:51:02 2020 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Jun 23 22:51:02 2020 -0700"
  },
  "message": "Support python interpreter target in pip_import. (#312)\n\n* Support python interpreter target in pip_import.\r\n\r\nThis allows users to use a custom python interpreter that is built by\r\nanother repository rule instead of using a pre-built interpreter binary\r\nthat is checked-in.\r\n\r\nThis tangentially addresses #257 since a common setup is to use the\r\ncustom built interpreter in the python toolchain.\r\n\r\nFor example, see: https://github.com/kku1993/bazel-hermetic-python\r\n\r\n* Actually use interpreter path.\r\n\r\nCo-authored-by: Andy Scott \u003candyscott@users.noreply.github.com\u003e",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8d8b0f5c9be19001e7c8168d25185073a958770d",
      "old_mode": 33261,
      "old_path": "docs/pip.md",
      "new_id": "8bffb114cd8b9ec1aa9460ac5bcd9926f06c7d2e",
      "new_mode": 33261,
      "new_path": "docs/pip.md"
    },
    {
      "type": "modify",
      "old_id": "60793fd33b3a4fa5d372006fdd40b97f62a59dd9",
      "old_mode": 33188,
      "old_path": "python/pip.bzl",
      "new_id": "e6c8f632f26438687483e7a159ca575ad7479cc4",
      "new_mode": 33188,
      "new_path": "python/pip.bzl"
    }
  ]
}