)]}'
{
  "commit": "a60f7a19c0b418fe95fcf2ec0957005ae39e1090",
  "tree": "f39bebcd19cd20a4975a000d409f033a1b6d2abe",
  "parents": [
    "ee98abd7d7bd2ca9c7b98aa19164fd0306a3f3d2"
  ],
  "author": {
    "name": "Anish Athalye",
    "email": "me@anishathalye.com",
    "time": "Wed Jan 22 16:07:06 2020 -0500"
  },
  "committer": {
    "name": "Ingy döt Net",
    "email": "ingy@ingy.net",
    "time": "Wed Jan 13 17:51:32 2021 -0500"
  },
  "message": "Fix compatibility with Jython\n\nThis patch was taken from\nhttps://github.com/yaml/pyyaml/issues/369#issuecomment-571596545,\nauthored by Pekka Klärck \u003cpeke@iki.fi\u003e.\n\nIn short, Jython doesn\u0027t support lone surrogates, so importing yaml (and\nin particular, loading `reader.py`) caused a UnicodeDecodeError. This\npatch works around this through a clever use of `eval` to defer\nevaluation of the string containing the lone surrogates, only doing it\non non-Jython platforms.\n\nThis is only done in `lib/yaml/reader.py` and not `lib3/yaml/reader.py`\nbecause Jython does not support Python 3.\n\nWith this patch, Jython\u0027s behavior with respect to Unicode code points\nover 0xFFFF becomes as it was before\n0716ae21a1e7ab6b4ef73428c0c8fff49685d057. It still does not pass all the\nunit tests on Jython (passes 1275, fails 3, errors on 1); all the\nfailing tests are related to unicode. Still, this is better than simply\ncrashing upon `import yaml`.\n\nWith this patch, all tests continue to pass on Python 2 / Python 3.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4b377d61e29b35544933513867252f8c4ccc779b",
      "old_mode": 33188,
      "old_path": "lib/yaml/reader.py",
      "new_id": "4c42150989cec4ac44e3d378dbc67bfa153bc92f",
      "new_mode": 33188,
      "new_path": "lib/yaml/reader.py"
    }
  ]
}