Kconfiglib.git/kconfiglib.py, branch v12.2.1

Make 12.2.1 release

2019-06-06T07:27:42Z

Adds commit 443e6bb ("menuconfig: Fix help display on Python 2").

Make 12.2.0 release

2019-06-06T03:32:37Z

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")

Update various comments now that menuconfig is Python 2-compatible

2019-06-06T02:57:22Z

Make 12.1.0 release

2019-06-04T09:00:13Z

Adds commit 22f2778 ("Mention that the load_config() message is different for replace=False")

Mention that the load_config() message is different for replace=False

2019-06-04T01:09:35Z

Handy to know when writing merging utilities.

Get rid of bare 'except:' in _save_old()

2019-06-03T05:21:32Z

Catch Exception instead, which avoids catching things like keyboard interrupts.

Improve warning control API (with backwards compatibility)

2019-06-03T04:50:06Z

A wart of the warning control API (enable/disable_*_warnings()) is that the current warning settings can't be queried. Querying warning settings is useful in functions that want to temporarily enable/disable some warning and then put things back to how they were. kconfiglib.load_allconfig() ran into this, for example. Make the internal warning control variables public (improve the naming at the same time), and encourage just setting them directly. Keep the old API for backwards compatibility. Also remove _warn_redun_assign() and _warn_override(). They're trivial and were called in a single place.

Have load_config() and write_(min_)config() return messages

2019-06-03T04:50:06Z

Hardcoding load_config() and write_(min_)config() to write any message to stdout is awkward, because it means that the message can't be easily reused when stdout is the wrong place to write it to (e.g. in menuconfig/guiconfig). This gets extra bad now that there's also the "No change to ..." message. Modify load_config() and write_(min_)config() to return the message as a string instead, and have them always return a message, instead of just when 'filename' is None and verbose=True. This makes things flexible and straightforward. Use the new behavior in menuconfig.py and guiconfig.py. They now show "No change to ..." when saving a file doesn't modify it. Tools that want to write messages to stdout should now do print(kconf.load_config()) / print(kconf.write_config()). There's no clean way to preserve perfect backwards compatibility here, but keep accepting the 'verbose' argument and print a deprecation warning if a value is ever passed for it. That way, scripts will keep running, though possibly with less output on stdout. This changes the meaning of the load_config() return value as well, though I suspect it was only ever used by the menuconfig/guiconfig interfaces. The new behavior applies for kconfiglib.VERSION >= (12, 0, 0).

Add kconfiglib.VERSION

2019-06-03T02:42:35Z

Holds a (, , ) tuple, e.g. (12, 0, 0).

Fix obscure crash with rsource and $srctree pointing to a symlink

2019-06-01T04:21:54Z

Sourcing a file with an absolute path and using rsource in it triggered a relpath() between the absolute path and $srctree. Since e.g. symlink/../bar/ = bar/ is not guaranteed for symlinks, this could lead to the rsource'd file not being found if $srctree pointed to a symlink. Switch to a simpler, more textual method for stripping $srctree from glob results, which should be robust against symlink shenanigans. This also makes the code a bit easier to follow. Discovered by Marc Herbert. Piggyback some minor cleanup.