Richard Neumann added the comment:
I am using loggers and sub-loggers (getChild()) in classes, which contain
sub-classes, wich contain sub-sub-classes and so on for complex data processing.
Hence I was using the logging library with sub-loggers to see in which of the
(sub-)classes things happen.
Most classes are, however, instanced for different configuration and are
represented by strings like {instance_config}@{class_name} where
{instance_config} often contains dots as separators for IDs.
Example:
INFO 1000@TerminalsSyncer : Aggregating customer data:
1031002@Facebook
INFO 1000@TerminalsSyncer : Aggregating virtual data:
v60.1031002@Config
INFO 1000@TerminalsSyncer : Aggregating virtual data:
v60.1031002@Presentation
WARNING 1000@TerminalsSyncer->1.1000@TerminalSyncer: Terminal 1.1000 is
offline
However, if you still think that this is not, what the logging library is meant
for, I'd appreciate to know.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26999>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
