From e7febaa3436d61b90c2f54ee4d143ac5c5530db8 Mon Sep 17 00:00:00 2001 From: Chris Larson Date: Wed, 5 Jan 2011 11:19:21 -0700 Subject: build: use logger.isEnabledFor, not getEffectiveLevel I think this is less confusing, and avoids needing to know about the *range* of logging levels, instead simply asking what we really want to know. (Bitbake rev: dc2264387617586b5c0a61e126c75edde5e7abcd) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie --- bitbake/lib/bb/build.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'bitbake/lib/bb') diff --git a/bitbake/lib/bb/build.py b/bitbake/lib/bb/build.py index 96e4e2f07..2d8fe8be8 100644 --- a/bitbake/lib/bb/build.py +++ b/bitbake/lib/bb/build.py @@ -216,7 +216,7 @@ def exec_func_shell(function, d, runfile, cwd=None): with open(runfile, 'w') as script: script.write('#!/bin/sh -e\n') - if logger.getEffectiveLevel() <= logging.DEBUG: + if logger.isEnabledFor(logging.DEBUG): script.write("set -x\n") data.emit_func(function, script, d) @@ -230,7 +230,7 @@ def exec_func_shell(function, d, runfile, cwd=None): cmd = runfile - if logger.getEffectiveLevel() <= logging.DEBUG: + if logger.isEnabledFor(logging.DEBUG): logfile = LogTee(logger, sys.stdout) else: logfile = sys.stdout -- cgit v1.2.3