Kconfiglib.git/testsuite.py, branch v11.9.0Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v11.9.02019-05-29T00:47:44ZConvert docstrings to comments in testsuite.py2019-05-29T00:47:44ZUlf Magnussonulfalizer@gmail.com2019-05-29T00:45:35Zurn:sha1:15de4c0c9924cfeef1553fde21cb9b9e288f6238
Like was done a long time ago in kconfiglib.py. These functions are not
part of a standalone API.
Keep the docstrings for the compatibility tests, because those get
printed as the tests run.
Use the '<type> "prompt"' shorthand in __str__()2019-05-25T16:04:15ZUlf Magnussonulfalizer@gmail.com2019-05-25T15:04:09Zurn:sha1:9f57bf933508901f07d22c75fca42e62145f5512
Pro: Looks cleaner and matches how definitions are usually written.
Con: Makes it harder to discover that 'bool "foo"' is just shorthand for
'bool' + 'prompt "foo"' (though it's documented).
The pros probably win.
Display n/m/y without quotes2019-05-25T14:50:07ZUlf Magnussonulfalizer@gmail.com2019-05-25T14:49:35Zurn:sha1:e1da7aa4d041d25e4fd5fd1f603f4c28d32b1392
These are constant symbols, which is why the quotes showed up.
Special-case them to remove the quotes, to match what people expect.
Internally, n/m/y without quotes is taken as a shorthand for
"n"/"m"/"y".
Strip direct deps. from property conditions in Symbol/Choice/MenuNode.__str__()2019-05-25T14:18:29ZUlf Magnussonulfalizer@gmail.com2019-05-25T11:52:09Zurn:sha1:bb33eed5cc6bdce2b65aa570ecd9a400bcd9c180
Commit e81a77b ("Consistently put direct deps. last when propagating")
makes the position of the direct deps. in property conditions
predictable after dependency propagation, making it easy to strip them
as needed.
Use this to implement MenuNode.orig_{prompt,defaults,selects,implies,ranges},
which work like the non-orig_* versions but omit the direct deps. Use
those in turn to omit the direct deps in Symbol/Choice.__str__().
The direct deps. (with propagated parent deps.) can still be seen after
'depends on ...', so there is no loss of information.
This unclutters Kconfig definitions shown in menuconfig/guiconfig and in
any generated documentation. The old output also had duplicated
dependencies, though it doesn't matter for evaluation.
Before:
config A
bool
prompt "A" if DEP
default y if FOO && DEP
depends on DEP
After:
config A
bool
prompt "A"
default y if FOO
depends on DEP
Consistently put direct deps. last when propagating2019-05-24T11:08:12ZUlf Magnussonulfalizer@gmail.com2019-05-24T10:14:31Zurn:sha1:e81a77bdb0687b62f91d7dc4d5b84b443808c0a7
Preparation for some later additions. Previously, the 'visible if' deps
appeared to the right of the 'depends on' deps. Now, the direct deps
always appear last.
With this change, the prompt tuple is only updated once for any given
menu node too, which should be a tiny bit faster.
Touch up style a bit in test suite2019-05-24T10:21:54ZUlf Magnussonulfalizer@gmail.com2019-05-24T10:20:18Zurn:sha1:e806f26a075ba52eca01567c7be7f0b4eba91df5
Ye olde code.
Give more helpful error messages when files are missing2019-03-06T02:51:04ZUlf Magnussonulfalizer@gmail.com2019-03-06T02:21:08Zurn:sha1:132e579cb8e4bdd49eb057ea81f5f8528ff80cf9
The current error message talks a lot about $srctree, but $srctree is
seldom the culprit in practice. More common is
'source "$(SOME_ENV_VAR)/foo"`, where SOME_ENV_VAR hasn't been set.
Include the complete 'source ...' line for missing Kconfig files, and
mention unset environment variables as a hint. Only mention $srctree
briefly.
Also shorten the message when a .config can't be a found a bit. This
message would usually only be seen when working directly with the
library.
Update copyright years for 20192019-01-15T22:12:10ZUlf Magnussonulfalizer@gmail.com2019-01-15T22:11:34Zurn:sha1:770abd61a5c90837d9336afd972090eebbc26b0bGet rid of _next_token() and _peek_token()2018-11-23T09:29:57ZUlf Magnussonulfalizer@gmail.com2018-11-23T00:33:32Zurn:sha1:ab89ef6aa7b8fef0eb410949c86a25e55586a972
These are pretty hot. Inline them to save a few % of parsing time.
They're pretty simple anyway.
_tokens_i was initialized to -1 to simplify the _next_token()
implementation. With _next_token() gone, initialize it to 0 instead,
which simplifies some other code.
Disable test dependent on dict ordering on Python 3.5 and earlier2018-11-21T10:34:32ZUlf Magnussonulfalizer@gmail.com2018-11-21T10:17:28Zurn:sha1:01757e5ac9324948ca64a4cf512352b09956a8fa
The KCONFIG_WARN_UNDEF test often fails on Python 3.4 (3.5 not tested),
but the output is still correct. It just differs due to dict ordering
randomness.
Python 3.6 iterates over dicts in insertion order in practice, and
Python 3.7 made it part of the spec, so enable the test for 3.6 and
later.
Python 2.7 seems fine as well.