Hi Bruno,
On 3/26/24 5:18 PM, Bruno Haible wrote:
> Yes. Sounds good.
Would you prefer one patch with all of the changes or one per file?
I'm happy either way, so whatever would make it easier for you if you
want to review the changes.
> I'm reluctant to add a dependency on yet another environment variable:
> - What if some users have it already set, for a different purpose?
> - What if users include options in this environment variable?
> - It makes remote problem analysis harder.
Yes, I agree. It would be nice not to have to ask for the output of
'env' or 'printenv' in bug reports. :)
It seems that Automake uses $PYTHON so I figured it was somewhat safe
to choose [1].
> You can use pre-built packages and use PATH to select the one:
>
> $ mkdir -p $HOME/choose-python/3.7
>
> $ ln -s /usr/bin/python3.7 $HOME/choose-python/3.7/python3
> or, if that does not work:
> $ { echo '#!/bin/sh'; echo 'exec /usr/bin/python3.7 "$@"'; } >
> $HOME/choose-python/3.7/python3
> $ chmod a+x $HOME/choose-python/3.7/python3
>
> $ PATH=$HOME/choose-python/3.7:$PATH
>
> Admittedly this is a little bit more complicated (for you) than setting
> an environment variable.
I'm perfectly happy with changing the gnulib-tool script to test that
it remains compatible with Python 3.7. The suggestion of an
environment variable was more for others. I wasn't aware that you
already had a solution to deal with stuff like this. Thanks for the
example, I'll probably try it.
Since it is just you and I testing we can leave it as is. In the
future if running different Python versions is something that is
necessary, we can think of a better solution than environment
variables.
[1] https://git.savannah.gnu.org/cgit/automake.git/tree/m4/python.m4#n61
Collin
