Antoine Pitrou added the comment: Well, I have met this problem too some time ago, so could you please reopen the bug?
Saying creating a lot of connection-bound logger objects is an "antipattern" doesn't help. It's the only simple way of doing something useful: have a logging target with different messages based on IP address (or whatever else, e.g. user name). Also, when you say "changes made to logging after this issue was created make it easier to include context information (e.g. connection IDs) in logging calls", that doesn't address the problem, because you have to include that "context information" in every logging class while what you really want to do is to include it once in the call to getLogger()... ____________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue932563> ____________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
