doc: mention pyenv.

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

diff --git a/HACKING b/HACKING
index 5e6aabaa2f350eb6a43c4bf5d4c2c7e66c452082..ed644ea9f481f85a3cab2c1cada4bbd677e52352 100644 (file)
--- 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