Kconfiglib.git, branch main

ci: Disable macos-13 runner

2026-02-02T10:16:32Z

macos-13 runner has been retired. macos-14 runner has only Python 3.10 and newer. This commit disables macos-13 runner and thus also Python 3.9 testing on macOS. Signed-off-by: Torsten Rasmussen

drop support for Python 2.x as it is very much EOL

2026-02-02T07:22:15Z

A follow-up to b96a5ad562deffa697d966c29546650aae645f48 where we stopped having CI run tests on Python 2.x. This actually drops the few remaining Python 2.x compatibility bits as Python 2.x has EOL'd a long time ago. Signed-off-by: Benjamin Cabé Signed-off-by: Torsten Rasmussen

guiconfig: Add dark mode

2025-12-04T13:52:35Z

TK under Windows/Linux did not have a native support for dark mode. Signed-off-by: Yves Wang

scripts: kconfig: gnuconfig: Ignore loc

2025-11-04T13:38:55Z

The commit 125d0daaa17aa added 'loc' to the sym.ranges tuples and fixed kconfiglib.py but guiconfig.py is left untouched. This make menuconfig to die with: Exception in Tkinter callback Traceback (most recent call last): File "/usr/lib/python3.13/tkinter/__init__.py", line 2077, in __call__ return self.func(*args) ~~~~~~~~~^^^^^^^ File ".../scripts/kconfig/guiconfig.py", line 917, in _tree_double_click return _tree_enter(event) File ".../scripts/kconfig/guiconfig.py", line 942, in _tree_enter _change_node(node, tree.winfo_toplevel()) ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File ".../scripts/kconfig/guiconfig.py", line 1125, in _change_node s = _set_val_dialog(node, parent) File ".../scripts/kconfig/guiconfig.py", line 1219, in _set_val_dialog range_info = _range_info(sym) File ".../scripts/kconfig/guiconfig.py", line 1339, in _range_info for low, high, cond in sym.ranges: ^^^^^^^^^^^^^^^ ValueError: too many values to unpack (expected 3) This commit ignores the last element in the tuples. Signed-off-by: Yasushi SHOJI

scripts: kconfig: menuconfig: Ignore loc

2025-11-04T13:38:55Z

The commit 125d0daaa17aa added 'loc' to the sym.ranges tuples and fixed kconfiglib.py but menuconfig.py is left untouched. This make menuconfig to die with: Traceback (most recent call last): File ".../scripts/kconfig/menuconfig.py", line 3284, in _main() ~~~~~^^ File ".../scripts/kconfig/menuconfig.py", line 663, in _main menuconfig(standard_kconfig(__doc__)) ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ File ".../scripts/kconfig/menuconfig.py", line 732, in menuconfig print(curses.wrapper(_menuconfig)) ~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.13/curses/__init__.py", line 94, in wrapper return func(stdscr, *args, **kwds) File ".../scripts/kconfig/menuconfig.py", line 872, in _menuconfig _change_node(sel_node) ~~~~~~~~~~~~^^^^^^^^^^ File ".../scripts/kconfig/menuconfig.py", line 1586, in _change_node s, _range_info(sc)) ~~~~~~~~~~~^^^^ File ".../scripts/kconfig/menuconfig.py", line 3119, in _range_info for low, high, cond in sym.ranges: ^^^^^^^^^^^^^^^ ValueError: too many values to unpack (expected 3) This commit ignores the last element in the tuples. Signed-off-by: Yasushi SHOJI

kconfiglib: Fix file leaks

2025-10-28T08:03:31Z

Fixing a couple cases of a programming error where a file is not closed in case of an exception, which was causing resource leak warnings in some cases when encountering a kconfig error. Signed-off-by: Declan Snyder Signed-off-by: Benjamin Cabé

fix crash caused by unsupported locales

2025-10-21T18:34:23Z

menuconfig: check if current menu is visible in parent when leaving

2025-10-21T18:33:24Z

This handles a case of leaving a menu which is not shown by the parent menu. This might occur, for instance, when searching for the symbol of a named choice, which is extended by an invisible symbol somewhere else.

kconfiglib: check empty strings on macro expansion

2025-10-21T13:57:55Z

During macro expansion, bare macros on a line are accepted by the parser as long as they resolve to blank strings. The problem is that the script is currently checking using isspace, so it's actually not checking for blank strings. This causes the parsing to fail when a macro is the last line of a file, and no newline character is added afterwards. This patch adds a check for the string itself being empty.

scripts: menuconfig: proper handling of NULL character as input

2025-10-21T12:31:14Z

Fixes: https://github.com/zephyrproject-rtos/zephyr/issues/33212 Ignoring when user inputs NULL in a text field. menuconfig exits with a python stack trace if NULL is provided as input character, therefore ignore NULL as an input character to prevent this behaviour. A NULL character may be given accidentally by the user through the following ways: - Pressing `Win` key on keyboard (Windows only) - Pressing `-@` / `-2`. Signed-off-by: Torsten Rasmussen