From 2f120f1b6d5763c1f00f00f5e78da860c053da88 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Tue, 30 Jan 2024 15:10:21 -0800 Subject: [PATCH] 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 should usually be provided (but for short or trivial changes), and should follow the GNU guidelines -- 2.47.3