Re: transition git-hooks on sourceware.org to Python 3.x

[Joel Brobecker <brobecker@adacore.com>]

> > For this, what I'd like to propose is that we use a set of wrapper
> > scripts which provide the same hooks as the git-hooks, and which
> > only do the following: add the correct Python to the PATH, and
> > then call the real hook script in git-hooks.
> 
> Adding to PATH, or other such variables, seems like it would also affect 
> external programs in hooks-bin run via configuration settings in the hooks 
> configuration (where those use "#! /usr/bin/env python3" or "#! 
> /usr/bin/env python", for example).  Have you concluded that this will 
> work OK for the existing hooks-bin code for the various repositories 
> (including the use of packages in 
> /home/gccadmin/.local/lib/python3.6/site-packages from GCC's 
> commit_checker script)?

I haven't no. I can do some testing if you tell me what testing
needs to be done. For now, I haven't been able to see the scripts
because they are in a location I do not have permissions to read.
Or, alternatively, we can agree on the location of the git-wrappers,
I can prepare a first version of the venv, and let you know when
it's ready, so you can do some testing, and then migrate to that
when you have done sufficient testing.

For the .local/lib/python3.6/site-packages, I propose we include
them into the venv that we create for the wrapper. The README.md
gives a list of all the Python packages we want to have, so I can
add those used by GCC.

-- 
Joel