| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -385,21 +385,39 @@ have specific values relative to the predefined levels. If you define a level | |||
| 385 | 385 | with the same numeric value, it overwrites the predefined value; the predefined | |
| 386 | 386 | name is lost. | |
| 387 | 387 | ||
| 388 | - +-----------------------+---------------+ | ||
| 389 | - | Level | Numeric value | | ||
| 390 | - +=======================+===============+ | ||
| 391 | - | .. py:data:: CRITICAL | 50 | | ||
| 392 | - +-----------------------+---------------+ | ||
| 393 | - | .. py:data:: ERROR | 40 | | ||
| 394 | - +-----------------------+---------------+ | ||
| 395 | - | .. py:data:: WARNING | 30 | | ||
| 396 | - +-----------------------+---------------+ | ||
| 397 | - | .. py:data:: INFO | 20 | | ||
| 398 | - +-----------------------+---------------+ | ||
| 399 | - | .. py:data:: DEBUG | 10 | | ||
| 400 | - +-----------------------+---------------+ | ||
| 401 | - | .. py:data:: NOTSET | 0 | | ||
| 402 | - +-----------------------+---------------+ | ||
| 388 | + +-----------------------+---------------+-------------------------------------+ | ||
| 389 | + | Level | Numeric value | What it means / When to use it | | ||
| 390 | + +=======================+===============+=====================================+ | ||
| 391 | + | .. py:data:: NOTSET | 0 | When set on a logger, indicates that| | ||
| 392 | + | | | ancestor loggers are to be consulted| | ||
| 393 | + | | | to determine the effective level. | | ||
| 394 | + | | | If that still resolves to | | ||
| 395 | + | | | :const:`!NOTSET`, then all events | | ||
| 396 | + | | | are logged. When set on a handler, | | ||
| 397 | + | | | all events are handled. | | ||
| 398 | + +-----------------------+---------------+-------------------------------------+ | ||
| 399 | + | .. py:data:: DEBUG | 10 | Detailed information, typically only| | ||
| 400 | + | | | of interest to a developer trying to| | ||
| 401 | + | | | diagnose a problem. | | ||
| 402 | + +-----------------------+---------------+-------------------------------------+ | ||
| 403 | + | .. py:data:: INFO | 20 | Confirmation that things are working| | ||
| 404 | + | | | as expected. | | ||
| 405 | + +-----------------------+---------------+-------------------------------------+ | ||
| 406 | + | .. py:data:: WARNING | 30 | An indication that something | | ||
| 407 | + | | | unexpected happened, or that a | | ||
| 408 | + | | | problem might occur in the near | | ||
| 409 | + | | | future (e.g. 'disk space low'). The | | ||
| 410 | + | | | software is still working as | | ||
| 411 | + | | | expected. | | ||
| 412 | + +-----------------------+---------------+-------------------------------------+ | ||
| 413 | + | .. py:data:: ERROR | 40 | Due to a more serious problem, the | | ||
| 414 | + | | | software has not been able to | | ||
| 415 | + | | | perform some function. | | ||
| 416 | + +-----------------------+---------------+-------------------------------------+ | ||
| 417 | + | .. py:data:: CRITICAL | 50 | A serious error, indicating that the| | ||
| 418 | + | | | program itself may be unable to | | ||
| 419 | + | | | continue running. | | ||
| 420 | + +-----------------------+---------------+-------------------------------------+ | ||
| 403 | 421 | ||
| 404 | 422 | ||
| 405 | 423 | .. _handler: | |
0 commit comments