Ben Feinstein added the comment:
General loggers are used in the standard way (message, args, etc), but data
loggers are used for different types of data. Instead of message, they
receive the experiment results (dict/list/np.array/binary data) and their
`formatMessage()` method should be
Ben Feinstein added the comment:
I use the logging module to log records of lab experiments. I have two
types of loggers, one for experiment results ("data") and another for
general information. I think that having a different managers for data
loggers is the easiest way to do it.
O
Ben Feinstein added the comment:
Here is a code that demonstrate the bug:
```python
import logging
class LogRecordTypeFilter(logging.Filter):
def __init__(self, cls):
self.cls = cls
def filter(self, record):
t = type(record)
if t is not self.cls
Change by Ben Feinstein :
Removed file: https://bugs.python.org/file47478/issue_logRecordFactory.py
___
Python tracker
<https://bugs.python.org/issue33057>
___
___
Pytho
Change by Ben Feinstein :
--
keywords: +patch
pull_requests: +5848
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue33057>
___
___
Py
New submission from Ben Feinstein :
In logging.Manager, the logRecordFactory attribute is never used.
One would expect that makeRecord() (in logging.Logger) would generate a record
using its manager's logRecordFactory, or fallback to the global
_logRecordFactory (if has no manage
