summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-12-11 12:07:58 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-07 14:43:25 +0000
commited0a240e1632682ec4c33341f3e24ad71773cdfc (patch)
tree201557f498b77b9f51fad7e12a6009f74aca4c65 /documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html
parentaf19d889ef320f9625aae42eed6688b5cc739793 (diff)
downloadpoky-ed0a240e1632682ec4c33341f3e24ad71773cdfc.tar.gz
documentation: Rename of poky-ref-manual folder to ref-manual.
Changing the folder that holds the YP Reference Manual to be "ref-manual". This will help with confustion over the manual's intended purpose. (From yocto-docs rev: 1106442964b5080cb0b6b3bd3af32e9407c0f7c1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html')
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html45
1 files changed, 45 insertions, 0 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html
new file mode 100644
index 0000000000..e57b647148
--- /dev/null
+++ b/documentation/ref-manual/eclipse/html/poky-ref-manual/logging-with-python.html
@@ -0,0 +1,45 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>2.3.7.1. Logging With Python</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="recipe-logging-mechanisms.html" title="2.3.7. Recipe Logging Mechanisms">
9<link rel="prev" href="recipe-logging-mechanisms.html" title="2.3.7. Recipe Logging Mechanisms">
10<link rel="next" href="logging-with-bash.html" title="2.3.7.2. Logging With Bash">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.7.1. Logging With Python">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="logging-with-python"></a>2.3.7.1. Logging With Python</h4></div></div></div>
15<p>
16 When creating recipes using Python and inserting code that handles build logs
17 keep in mind the goal is to have informative logs while keeping the console as
18 "silent" as possible.
19 Also, if you want status messages in the log use the "debug" loglevel.
20 </p>
21<p>
22 Following is an example written in Python.
23 The code handles logging for a function that determines the number of tasks
24 needed to be run:
25 </p>
26<pre class="literallayout">
27 python do_listtasks() {
28 bb.debug(2, "Starting to figure out the task list")
29 if noteworthy_condition:
30 bb.note("There are 47 tasks to run")
31 bb.debug(2, "Got to point xyz")
32 if warning_trigger:
33 bb.warn("Detected warning_trigger, this might be a problem later.")
34 if recoverable_error:
35 bb.error("Hit recoverable_error, you really need to fix this!")
36 if fatal_error:
37 bb.fatal("fatal_error detected, unable to print the task list")
38 bb.plain("The tasks present are abc")
39 bb.debug(2, "Finished figuring out the tasklist")
40 }
41 </pre>
42<p>
43 </p>
44</div></body>
45</html>