Message332117
| Author | eamanu |
|---|---|
| Recipients | eamanu, porton, steven.daprano, vinay.sajip |
| Date | 2018-12-19.10:02:38 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1545213758.22.0.788709270274.issue35530@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> The call to logging.error() is irrelevant, since there's no expectation that the module-level function will necessarily output the same as a method of a specific instance logger.error(). That's true. Maybe and warning or Exception can be raise? > It looks like a bug to *me*, but I'm not a logging expert. I'm seeing the same behaviour in 3.5 and 3.7, but in 2.7.1 the first call to logger.error prints an error message: and 3.8? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-12-19 10:02:38 | eamanu | set | recipients: + eamanu, vinay.sajip, steven.daprano, porton |
| 2018-12-19 10:02:38 | eamanu | set | messageid: <1545213758.22.0.788709270274.issue35530@psf.upfronthosting.co.za> |
| 2018-12-19 10:02:38 | eamanu | link | issue35530 messages |
| 2018-12-19 10:02:38 | eamanu | create | |