[automake-commit] branch master updated: doc: mention pyenv.

[Karl Berry]

This is an automated email from the git hooks/post-receive script.

karl pushed a commit to branch master
in repository automake.

View the commit online:
https://git.savannah.gnu.org/gitweb/?p=automake.git;a=commitdiff;h=2f120f1b6d5763c1f00f00f5e78da860c053da88

The following commit(s) were added to refs/heads/master by this push:
     new 2f120f1b6 doc: mention pyenv.
2f120f1b6 is described below

commit 2f120f1b6d5763c1f00f00f5e78da860c053da88
Author: Karl Berry <karl@freefriends.org>
AuthorDate: Tue Jan 30 15:10:21 2024 -0800

    doc: mention pyenv.
    
    * HACKING: mention pyenv as a way to test different Python versions.
---
 HACKING | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/HACKING b/HACKING
index 5e6aabaa2..ed644ea9f 100644
--- a/HACKING
+++ b/HACKING
@@ -84,6 +84,9 @@
      env PERL5LIB=$am/lib $am/bin/automake --help
      env PERL5LIB=$am/lib $am/bin/aclocal --help
 
+* If you need to test different Python versions, pyenv is probably the
+  most convenient way at this writing. https://github.com/pyenv
+
 ============================================================================
 = Naming
 
@@ -306,7 +309,7 @@
   git log or the ChangeLog file from a release tarball. There are no
   hard-and-fast rules; the aim is a usable description. So script
   names, Makefile targets, and more are all viable. Some examples:
-  aclocal automake build cosmetics doc maint python release tests  ylwrap
+  aclocal automake build cosmetics doc maint python release test ylwrap
 
 * The <detailed list of touched files> should usually be provided (but
   for short or trivial changes), and should follow the GNU guidelines