| commit | f7c51606f0eae56f0cf52c54713f7816d8e9f97c | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@google.com> | Tue Jun 18 17:23:39 2019 -0400 |
| committer | Mike Frysinger <vapier@google.com> | Sat Jul 27 01:10:40 2019 +0000 |
| tree | 0ed377b68aa43d1440d738cb4fe176e08bca218d | |
| parent | 745be2ede1e67421275afc00c04d996d9d6908ee [diff] |
hooks: support external hooks running different Python version As we convert repo to support Python 3, the version of Python that we use might not be the version that repo hooks users have written for. Since repo upgrades are not immediate, and not easily under direct control of end users (relative to the projects maintaining the hook code), allow hook authors to declare the version of Python that they want to use. Now repo will read the shebang from the hook script and compare it against the version of Python repo itself is running under. If they differ, we'll try to execute a separate instance of Python and have it load & execute the hook. If things are compatible, then we still use the inprocess execution logic that we have today. This allows repo hook users to upgrade on their own schedule (they could even upgrade to Python 3 ahead of us) without having to worry about their supported version being exactly in sync with repo's. Bug: https://crbug.com/gerrit/10418 Change-Id: I97c7c96b64fb2ee465c39b90e9bdcc76394a146a Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/228432 Reviewed-by: David Pursehouse <dpursehouse@collab.net> Tested-by: Mike Frysinger <vapier@google.com>
Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.