log import updated

2637f3c9 · Felipe Delestro Matos · f83ffcf9 · 2637f3c9
Commit 2637f3c9 authored May 25, 2023 by Felipe Delestro Matos
--- a/docs/notebooks/Logging.ipynb
+++ b/docs/notebooks/Logging.ipynb
@@ -2,15 +2,14 @@
 "cells": [
  {
   "cell_type": "markdown",
-   "id": "24c15e5d",
+   "id": "ae2a75fe",
   "metadata": {},
   "source": [
    "# Logging system for qim3d\n",
-    "Using proper logging instead of print statements is a recommended practice in software development for a variety of reasons. \n",
    "\n",
-    "While print statements can be helpful for quick debugging, logging provides a more powerful and versatile approach. \n",
+    "Using proper logging instead of print statements is a recommended practice.\n",
    "\n",
-    "Logging allows for better control over output, with options to configure log levels, filter messages, and redirect output to different destinations. \n"
+    "While print statements can be helpful for quick debugging, logging provides a more powerful and versatile approach. Logging allows for better control over output, with options to configure log levels, filter messages, and redirect output to different destinations. \n"
   ]
  },
  {
@@ -26,13 +25,13 @@
   "outputs": [],
   "source": [
    "import qim3d\n",
-    "log = qim3d.log"
+    "from qim3d import log"
   ]
  },
  {
   "cell_type": "code",
   "execution_count": 2,
-   "id": "8a2b7c0e",
+   "id": "94022824",
   "metadata": {},
   "outputs": [
    {
@@ -88,7 +87,7 @@
  {
   "cell_type": "code",
   "execution_count": 4,
-   "id": "2824aa8a",
+   "id": "eb542404",
   "metadata": {},
   "outputs": [
    {
@@ -169,7 +168,7 @@
  {
   "cell_type": "code",
   "execution_count": 7,
-   "id": "20857afc",
+   "id": "eaceb5b6",
   "metadata": {},
   "outputs": [
    {

-%% Cell type:markdown id:24c15e5d tags:
+%% Cell type:markdown id:ae2a75fe tags:

 # Logging system for qim3d
-Using proper logging instead of print statements is a recommended practice in software development for a variety of reasons.

-While print statements can be helpful for quick debugging, logging provides a more powerful and versatile approach.
+Using proper logging instead of print statements is a recommended practice.

-Logging allows for better control over output, with options to configure log levels, filter messages, and redirect output to different destinations.
+While print statements can be helpful for quick debugging, logging provides a more powerful and versatile approach. Logging allows for better control over output, with options to configure log levels, filter messages, and redirect output to different destinations.

 %% Cell type:code id:a31b2245 tags:

 ``` python
 import qim3d
-log = qim3d.log
+from qim3d import log
 ```

-%% Cell type:code id:8a2b7c0e tags:
+%% Cell type:code id:94022824 tags:

 ``` python
 # Here we test by sending one message for each level
 # Note that DEBUG and INFO do not appear
 log.debug('debug level message')
 log.info('info level message')
 log.warning('warning level message')
 log.error('error level message')
 log.critical('critical level message')
 ```

 %% Output

    warning level message
    error level message
    critical level message

 %% Cell type:code id:b0856333 tags:

 ``` python
 # Change the level to debug
 qim3d.io.logger.set_level_DEBUG()

 # Now all the levels get logged
 log.debug('debug level message')
 log.info('info level message')
 log.warning('warning level message')
 log.error('error level message')
 log.critical('critical level message')
 ```

 %% Output

    debug level message
    info level message
    warning level message
    error level message
    critical level message

-%% Cell type:code id:2824aa8a tags:
+%% Cell type:code id:eb542404 tags:

 ``` python
 # Change the level to error
 qim3d.io.logger.set_level_ERROR()

 # And now only above ERROR is shown
 log.debug('debug level message')
 log.info('info level message')
 log.warning('warning level message')
 log.error('error level message')
 log.critical('critical level message')
 ```

 %% Output

    error level message
    critical level message

 %% Cell type:code id:af3cc812 tags:

 ``` python
 # We can increase the level of detail
 qim3d.io.logger.set_detailed_output()

 # Note that DEBUG and INFO are still not shown
 log.debug('debug level message')
 log.info('info level message')
 log.warning('warning level message')
 log.error('error level message')
 log.critical('critical level message')
 ```

 %% Output

    ERROR     3224913348.py:8    error level message
    CRITICAL  3224913348.py:9    critical level message

 %% Cell type:code id:d7239b1b tags:

 ``` python
 # We can switch back to the simple output mode
 qim3d.io.logger.set_simple_output()

 # Now we see all the levels on simple mode
 log.debug('debug level message')
 log.info('info level message')
 log.warning('warning level message')
 log.error('error level message')
 log.critical('critical level message')
 ```

 %% Output

    error level message
    critical level message

-%% Cell type:code id:20857afc tags:
+%% Cell type:code id:eaceb5b6 tags:

 ``` python
 # Change back to detailed and DEBUG level
 qim3d.io.logger.set_detailed_output()
 qim3d.io.logger.set_level_DEBUG()

 log.debug('debug level message')
 log.info('info level message')
 log.warning('warning level message')
 log.error('error level message')
 log.critical('critical level message')
 ```

 %% Output

    DEBUG     4221232047.py:5    debug level message
    INFO      4221232047.py:6    info level message
    WARNING   4221232047.py:7    warning level message
    ERROR     4221232047.py:8    error level message
    CRITICAL  4221232047.py:9    critical level message