From: Karl Berry <karl@freefriends.org>
Date: Tue, 30 Jan 2024 23:10:21 +0000 (-0800)
Subject: doc: mention pyenv.
X-Git-Tag: v1.16.90~14
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2f120f1b6d5763c1f00f00f5e78da860c053da88;p=thirdparty%2Fautomake.git

doc: mention pyenv.

* HACKING: mention pyenv as a way to test different Python versions.
---

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