Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
openstructure
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container registry
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
schwede
openstructure
Commits
7cc28c8b
Commit
7cc28c8b
authored
13 years ago
by
Marco Biasini
Browse files
Options
Downloads
Patches
Plain Diff
document new behaviour of logging system
parent
b21aa572
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
modules/base/doc/logging.rst
+15
-1
15 additions, 1 deletion
modules/base/doc/logging.rst
with
15 additions
and
1 deletion
modules/base/doc/logging.rst
+
15
−
1
View file @
7cc28c8b
...
@@ -14,7 +14,17 @@ OpenStructure has a logging system going beyond what print statements can offer.
...
@@ -14,7 +14,17 @@ OpenStructure has a logging system going beyond what print statements can offer.
see :ref:`picking-logging-level`.
see :ref:`picking-logging-level`.
:param message: The message to be logged
:param message: The message to be logged
:type message: str
:type message: convertible to string
Similar to the built-int print function, several arguments can be passed to
the logging functions. The arguments will be converted to string and then
concatenated together, separated by space. For example:
.. code-block:: python
LogMessage('here be numbers', 1, 2)
will be converted to 'here be numbers 1 2'.
.. note::
.. note::
...
@@ -125,6 +135,10 @@ To change the current log sink you can use the following methods:
...
@@ -125,6 +135,10 @@ To change the current log sink you can use the following methods:
Change the log sink back to the previous one. It is an error to pop the log
Change the log sink back to the previous one. It is an error to pop the log
sink when there is only one log sink on the stack.
sink when there is only one log sink on the stack.
.. method:: GetCurrentLogSink()
Get the current (active) log sink.
.. _picking-logging-level:
.. _picking-logging-level:
Guidelines for picking logging level
Guidelines for picking logging level
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment