)]}'
{
  "commit": "af366c0d53b3cfe1bed1baba4e2869460276eb81",
  "tree": "e1977a96e149415867514bc1dae681d2add5a7fe",
  "parents": [
    "619d9bdf7ae70ce953f1a10aebccfdc3526b7200"
  ],
  "author": {
    "name": "Matt Bogosian",
    "email": "matt@bogosian.net",
    "time": "Mon Jan 24 07:11:55 2022 -0600"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Jan 24 21:11:55 2022 +0800"
  },
  "message": "Explain generic `Protocol[T1, T2, ...]` shorthand in Mypy docs (#12047)\n\nAs far as I can tell, the nugget exposed by this commit lives only in PEP 544. This\r\ncopies that nugget closer to where it is likely to be spotted by the intended audience.\r\n\r\nPEPs may not be accessible to customers who reasonably expect relevant information to be\r\nsurfaced in featured documentation. Even if customers are aware of PEPs, they may not\r\nthink to look there, and don\u0027t likely consider them primary sources. It is reasonable to\r\nassume that is the job of the docs, with PEPs capturing more esoteric nuances,\r\nrationales and other then-relevant details of decision-making, etc. It\u0027s also reasonable\r\nto expect that where further study may be helpful, links from relevant sections of\r\nprimary sources to secondary materials like PEPs should exist. This commit fills in both\r\ngaps for the subject shorthand.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7e64aa1814038b38ab823d1e85f2c3178d42c2e4",
      "old_mode": 33188,
      "old_path": "docs/source/generics.rst",
      "new_id": "7730bd0e5c108272a7589debbb1e8cf03d3709d6",
      "new_mode": 33188,
      "new_path": "docs/source/generics.rst"
    }
  ]
}