)]}'
{
  "commit": "1a2fb076ea2a00afce27a076bad5a8a655bd3bd3",
  "tree": "44b0d50ad991e2f3e2c662ce300d29d336e7895b",
  "parents": [
    "f84931c4908620c6f8fa897582ed2e72ba62f029"
  ],
  "author": {
    "name": "Yunze Xu",
    "email": "xyzinfernity@163.com",
    "time": "Mon Jun 12 10:08:12 2023 +0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Jun 12 10:08:12 2023 +0800"
  },
  "message": "[docs] Fix the incorrect API docs generation steps in the release process (#131)\n\n### Motivation\r\n\r\nhttps://github.com/apache/pulsar-client-python/pull/126 adds the\r\ninstruction to include the `_pulsar` C module when generating the API\r\ndocs. However, it does not work when the library is installed from\r\n`pip`. It only works when the wheel is installed from `dist/*.whl` that\r\nis generated by the `python3 setup.py bdist_wheel` command in the\r\nREADME.\r\n\r\nThe reason is the official Python wheel uses `auditwheel` to package all\r\ndynamic libraries, so the `_pulsar.so` depends on another dynamic\r\nlibrary in the relative path. e.g.\r\n\r\n```bash\r\n$ ldd ~/.local/lib/python3.8/site-packages/_pulsar.cpython-38-x86_64-linux-gnu.so\r\n        libpulsar-b6dad138.so \u003d\u003e /home/xyz/.local/lib/python3.8/site-packages/pulsar_client.libs/libpulsar-b6dad138.so (0x00007f8dc09b3000)\r\n        ...\r\n```\r\n\r\nIf we copy the `_pulsar.cpython-38-x86_64-linux-gnu.so` into the project\r\ndirectory, the `libpulsar-b6dad138.so` will not be found.\r\n\r\n### Modifications\r\n\r\nIn `RELEASE.md`, specify the path of `_pulsar.so` directly.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f3234145a23bf4a3124355ff1fc843af5f38541e",
      "old_mode": 33188,
      "old_path": "RELEASE.md",
      "new_id": "e9f9ea91daf2dfdad752b9f192797aca7eb52123",
      "new_mode": 33188,
      "new_path": "RELEASE.md"
    }
  ]
}