From 66832138bfb0e82190b55fb410104d969cbc829b Mon Sep 17 00:00:00 2001 From: Ulf Magnusson Date: Thu, 30 Aug 2018 08:37:59 +0200 Subject: Allow user values on 'option env' symbols Gets rid of a check, doesn't hurt. The check was added before 'option env' was changed to just add a 'default' under the hood. Note: New Kconfig code doesn't need 'option env'. Environment variables are now expanded directly, including in the C tools. 'option env' is only maintained for backwards compatibility. --- testsuite.py | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) (limited to 'testsuite.py') diff --git a/testsuite.py b/testsuite.py index e22c775..f7f75dd 100644 --- a/testsuite.py +++ b/testsuite.py @@ -1771,14 +1771,10 @@ tests/Krecursive2:1 os.environ["ENV_VAR"] = "ENV_VAR value" - # References undefined env. var. and tries to assign 'option env' variable, - # so disable warnings + # References undefined env. var., so disable warnings c = Kconfig("Kconfiglib/tests/Kmisc", warn=False) - # Verify that 'option env' symbols can't be assigned user values, and that - # 'option env' is treated like a default - assign_and_verify_user_value("FROM_ENV", "foo", None, False) - assign_and_verify_user_value("FROM_ENV_MISSING", "foo", None, False) + # Verify that 'option env' is treated like a default verify_value("FROM_ENV", "ENV_VAR value") verify_value("FROM_ENV_MISSING", "missing") -- cgit v1.2.3