)]}' { "commit": "4769b27af1374335f141d9929433d3fa60615c17", "tree": "1f13331e95e4d94c32f7e4fea8d8b9985edaae5d", "parents": [ "aa2b5e3385c4c9ac5053920546a97b8ec561edf5" ], "author": { "name": "Chad Norvell", "email": "chadnorvell@google.com", "time": "Tue Sep 20 05:05:02 2022 +0000" }, "committer": { "name": "CQ Bot Account", "email": "pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com", "time": "Tue Sep 20 05:05:02 2022 +0000" }, "message": "pw_ide: activate.py\n\nProvides a Python script that can be run independently of the Pigweed\nenvironment, and execute a given shell command *within* an activated\nPigweed environment.\n\nWhy do we need this? Editors aren\u0027t aware of the Pigweed environment,\nand neither are any subprocesses they spawn (unless you launch the\neditor *from* an activated environment, which you might do with vim but\nprobably wouldn\u0027t do from VS Code). We wrap tasks that need access to\nthe Pigweed environment in this script.\n\nNote that this script replicates much of the functionality already\npresent in the pw_env_setup module. The difference is that this script\ncan be run outside of the Pigweed environment and has no dependencies.\nIn the long run, we should find a way to merge the two in a way that\nworks for both use cases.\n\nChange-Id: Ic6741904c10d1a350f5ff318a52308fef87a006e\nReviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/110259\nReviewed-by: Anthony DiGirolamo \u003ctonymd@google.com\u003e\nCommit-Queue: Chad Norvell \u003cchadnorvell@google.com\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "0165529b58d87fa367aa9108294d102865b168c5", "old_mode": 33188, "old_path": "pw_ide/py/BUILD.gn", "new_id": "364ba1ca672cb482ef2f0891ea80d6e2d0450dae", "new_mode": 33188, "new_path": "pw_ide/py/BUILD.gn" }, { "type": "add", "old_id": "0000000000000000000000000000000000000000", "old_mode": 0, "old_path": "/dev/null", "new_id": "6c83a6b0085dfd70cfc9dc990d4585511a5f4eb2", "new_mode": 33188, "new_path": "pw_ide/py/pw_ide/activate.py" } ] }