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.

Author feinsteinben
Recipients feinsteinben, vinay.sajip
Date 2018-03-16.11:10:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CA+U30-D8jO-pcrT7ikRo0Mgm_CyZDhpSbqDKaxV7hyvUL5dHoA@mail.gmail.com>
In-reply-to <1521123714.68.0.467229070634.issue33057@psf.upfronthosting.co.za>
Content
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 modified in order to account for the
changed data-type.

This might indeed be an XY problem on my side. However, it seems that
someone already thought about it before and started implementing this
mechanism (`Manager.setLogRecordFactory()`), but didn't finish. That's why
I suggested this modification.

On Thu, Mar 15, 2018 at 4:21 PM Vinay Sajip <report@bugs.python.org> wrote:

>
> Vinay Sajip <vinay_sajip@yahoo.co.uk> added the comment:
>
> >  I have two types of loggers, one for experiment results ("data") and
> another for general information
>
> In what way is the behaviour of the two types of logger different? I'm
> concerned that this might be an XY problem ...
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue33057>
> _______________________________________
>
History
Date User Action Args
2018-03-16 11:10:26feinsteinbensetrecipients: + feinsteinben, vinay.sajip
2018-03-16 11:10:26feinsteinbenlinkissue33057 messages
2018-03-16 11:10:26feinsteinbencreate