Message157938
| Author |
vinay.sajip |
| Recipients |
desbma, vinay.sajip |
| Date |
2012年04月10日.07:33:59 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1334043240.72.0.130200953904.issue14539@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
You haven't configured any handlers for the logger, so by default it wouldn't actually log anything. However, when no handlers are configured, logging uses an internal "last resort" handler to print the message to sys.stderr, and this handler has a threshold of WARNING (it's meant to print stdlib warnings and errors when no handlers are configured by an application).
If you add the lines, you should see something like this:
>>> logging.basicConfig(level=logging.INFO, format='%(message)s')
>>> logging.info('info message')
info message
See
http://docs.python.org/py3k/howto/logging.html#what-happens-if-no-configuration-is-provided
for more information. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年04月10日 07:34:00 | vinay.sajip | set | recipients:
+ vinay.sajip, desbma |
| 2012年04月10日 07:34:00 | vinay.sajip | set | messageid: <1334043240.72.0.130200953904.issue14539@psf.upfronthosting.co.za> |
| 2012年04月10日 07:34:00 | vinay.sajip | link | issue14539 messages |
| 2012年04月10日 07:33:59 | vinay.sajip | create |
|