From fe91f478b5620235b8a462533850afef4731dac0 Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Thu, 6 Jun 2019 05:10:10 +0200 Subject: Make 12.2.0 release Do the opposite of what other people are doing and make menuconfig.py Python 2-compatible. Turns out it's not that tricky after all, and it makes everything consistently Python 2/3-compatible and streamlines things. - Commit 41b5891 ("menuconfig: Get rid of 'nonlocal'") - Commit b2e211d ("menuconfig: Fall back on getch() when get_wch() isn't available") - Commit c3162be ("menuconfig: Only decode curses.erasechar() on Python 3") - Commit fe6ed99 ("menuconfig: Import print_function for Python 2 compatibility") - Commit c209188 ("menuconfig: Have hashbang point to 'python' instead of 'python3'") - Commit d577865 ("Remove Python 3 menuconfig special-casing from Makefile patch") - Commit 319f7f0 ("Update various comments now that menuconfig is Python 2-compatible") - Commit 5fbd70e ("Update setup.py now that menuconfig is Python 2-compatible") Also investigate exactly what the Python version requirements are and tweak and document things a bit: - Commit e0baa79 ("Tweak python_requires to 2.7/3.2+") - Commit 3a772a6 ("Add a section on version compatibility to the README") --- README.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.rst') diff --git a/README.rst b/README.rst index 62d1b83..83563c7 100644 --- a/README.rst +++ b/README.rst @@ -96,7 +96,7 @@ Python 2 and Python 3. Previously, ``menuconfig.py`` only ran under Python 3 that your ``PATH`` includes the directory where the executables end up. You can list the installed files with ``pip(3) show -f kconfiglib``. -All releases have a corresponding tag in the git repository, e.g. ``v12.1.0`` +All releases have a corresponding tag in the git repository, e.g. ``v12.2.0`` (the latest version). `Semantic versioning `_ is used. There's been -- cgit v1.2.3