Kconfiglib.git/testsuite.py, branch v10.1.0

Flag extra tokens after 'if'/'depends on'/'visible if' expressions

2018-08-22T22:51:52Z

Extra trailing tokens after 'if ', 'depends on ', and 'visible if ' now trigger syntax errors instead of being ignored. Oversight. This indirectly makes Kconfig.eval_expr() detect extra trailing tokens as well.

Add a generic node iterator

2018-08-22T21:57:17Z

Suggested by Mitja Horvat (pinkfluid) in https://github.com/ulfalizer/Kconfiglib/pull/50. Kconfig.node_iter() iterates through all menu nodes in the menu tree in Kconfig order. This saves scripts the trouble of implementing their own tree walking code. Have node_iter() take a 'unique_syms' flag that can be enabled to only include symbols defined in multiple locations once. This is often what you want when generating output (and is used by write_config()). Order is still preserved. Piggyback a fix to a syntax error test comment. Parsing has been tightened up now.

Merge Symbol._checked and Symbol._written

2018-08-21T19:17:45Z

These are never used at the same time, and Symbol._visited is a good name for both. Gets rid of an internal attribute.

Handle multiple definition locations in a nicer way

2018-08-21T18:45:27Z

Instead of precalculating a set() to get unique symbols, precalculate a list with any duplicates from multiple definition locations removed, and preserve the order of the symbols within it. This makes it possible to get rid of the Symbol._written shenanigans in functions that only need to iterate through unique symbols in sorted order, which is all of them except write_config() (because it needs to walk the entire menu tree).

Fix header/minimal configuration ordering test

2018-08-21T13:40:53Z

Should test write_autoconf(), not write_config().

Make header symbol order match .config symbol order again

2018-08-21T13:19:52Z

I accidentally broke this when I added the _defined_syms_set optimization. No semantic difference, but having the order match is more readable.

Look up the top-level Kconfig file relative to $srctree

2018-08-18T01:15:46Z

Due to an old design braino, the top-level Kconfig filename passed to Kconfig.__init__() wasn't looked up relative to $srctree, breaking out-of-tree usage for e.g. menuconfig. Fixing it required ugliness like srctree = os.environ.get("srctree", "") kconfiglib.Kconfig(os.path.join(srctree, "Kconfig")) Change the behavior of Kconfig.__init__() to look up the top-level Kconfig file relative to $srctree. This means that all Kconfig files (both the top-level file and any source'd files) now use $srctree, which makes the vast majority of scripts just work when running out-of-tree. Also remove the note re. loading a subset of Kconfig files. Saying that the top-level file and all source'd Kconfig files are looked up relative to $srctree should make the behavior clear enough. Print a note about the new behavior whenever the top-level Kconfig file can't be opened, as this change could be breaking for some scripts. This is a slight backwards-compatiblity break, so the major version will be bumped.

Revert "Fix $srctree logic for the top-level Kconfig file"

2018-08-17T23:10:41Z

This reverts commit 8a3999bc708e8468ff79665e3cbdfccd603160e1. I realized that this should go in a major release at least, because it has the potential to break scripts that rely on the old behavior of ignoring $srctree for the filename passed to Kconfig.__init__(). A dummy release will bump the version to 9.4.2. Any future release with the change will be 10.0.0.

Fix $srctree logic for the top-level Kconfig file

2018-08-17T19:35:42Z

Due to a major design braino, the top-level Kconfig file passed to Kconfig.__init__() wasn't looked up relative to $srctree, breaking out-of-tree usage for e.g. menuconfig. With this change, Kconfig files are consistently looked up relative to $srctree, which makes a lot more sense. Also remove note re. loading a subset of Kconfig files. Saying that the top-level file and all source'd Kconfig files are looked up relative to $srctree should make the behavior clear enough.

Support custom printing of symbols/choices in expressions

2018-08-10T02:57:13Z

Allow custom output formats for symbols/choices when turning expressions into strings, via a user-supplied callback function (sc_str_fn). This makes things like turning symbols into links in generated documentation and displaying symbol values in the menuconfig interface less hacky to implement. Two new Symbol/Choice.custom_str() functions were added, as passing extra arguments to __str__() is awkward.