)]}'
{
  "commit": "4c365e71d1146f8f8f7c43ad19129c72ac49f4bf",
  "tree": "df6df3a44e69c9b3a212231f16d5da6e649f2942",
  "parents": [
    "7f6de725d99aa3dec9e2b20cfc038bdc4704cc1c"
  ],
  "author": {
    "name": "Richard Levasseur",
    "email": "rlevasseur@google.com",
    "time": "Fri Jun 02 15:13:18 2023 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Jun 02 22:13:18 2023 +0000"
  },
  "message": "cleanup: Set toolchain target_setting directly instead of via inline ternary (#1246)\n\nThe generated toolchain BUILD file is confusing to read because it\nrelies on a ternary expression in the BUILD file to set the\n`target_settings` attribute. This makes debugging harder because, upon\nfirst look, all the toolchains appear to have the version constraint\nset. It\u0027s only upon closer inspection that you can see the 1-character\ndifference of \"False\" vs \"True\" embedded into the middle of a line\namongst other similar looking lines.\n\nAlso:\n* Adds a bit of validation logic for the `set_python_version_constraint`\nargument\nbecause it\u0027s conceptually a boolean, but is passed as a string, so is\nprone to\n    having an incorrect value passed.\n* Documents the `set_python_version_constraint` arg, since it has a\nparticular range\n    of values it accepts.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b5ac81a491bd23715fd1c8231a279a37a90ca637",
      "old_mode": 33188,
      "old_path": "python/private/toolchains_repo.bzl",
      "new_id": "f47ea8f06422253f2e59589b38c3f95658cdd0c7",
      "new_mode": 33188,
      "new_path": "python/private/toolchains_repo.bzl"
    }
  ]
}