Message321583
| Author | vinay.sajip |
|---|---|
| Recipients | Michael Kearney, vinay.sajip, xtreak |
| Date | 2018-07-13.09:09:50 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1531472990.55.0.56676864532.issue34107@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This behaviour is as expected. If no handlers are configured for logging, an internal "handler of last resort" is used, with just the message output. See: https://docs.python.org/3/howto/logging.html#what-happens-if-no-configuration-is-provided If you call logging.warning(...), and if no handlers are configured, then basicConfig() is internally called to set up a handler with a basic format string. See: https://docs.python.org/3/library/logging.html#logging.log So, what you've described is as it should be. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-07-13 09:09:50 | vinay.sajip | set | recipients: + vinay.sajip, xtreak, Michael Kearney |
| 2018-07-13 09:09:50 | vinay.sajip | set | messageid: <1531472990.55.0.56676864532.issue34107@psf.upfronthosting.co.za> |
| 2018-07-13 09:09:50 | vinay.sajip | link | issue34107 messages |
| 2018-07-13 09:09:50 | vinay.sajip | create | |