This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: LoggerAdapter doesn't have fatal() like Logger
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 3.8, Python 3.7
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: Dave Johansen, SilentGhost, vinay.sajip
Priority: normal Keywords:

Created on 2019-05-29 23:03 by Dave Johansen, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (3)
msg343941 - (view) Author: Dave Johansen (Dave Johansen) Date: 2019-05-29 23:03
Using LoggerAdapter is a convenient way to add extra info to all logs, but it doesn't have the fatal() method like Logger, so it isn't a drop in replacement like it should be.
msg344069 - (view) Author: SilentGhost (SilentGhost) * (Python triager) Date: 2019-05-31 12:01
fatal is an undocumented feature, it's probably better not to use it in the first place.
msg344080 - (view) Author: Vinay Sajip (vinay.sajip) * (Python committer) Date: 2019-05-31 15:21
FATAL and fatal() are synonyms for CRITICAL and critical(), and they are only around because of backward compatibility constraints on the Logger class at the time logging was added to Python. Because LoggerAdapter has no backward compatibility constraints, fatal() wasn't provided there - but critical() is, and can be used equivalently.

Note that FATAL, fatal() are not documented as they are a legacy and not intended to be used - use CRITICAL and critical() instead.
History
Date User Action Args
2022-04-11 14:59:15adminsetgithub: 81273
2019-05-31 15:21:12vinay.sajipsetstatus: open -> closed
resolution: not a bug
messages: + msg344080

stage: resolved
2019-05-31 12:01:53SilentGhostsetnosy: + vinay.sajip, SilentGhost

messages: + msg344069
versions: + Python 3.8
2019-05-29 23:03:42Dave Johansencreate