[issue11950] logger use dict for loggers instead of WeakValueDictionary

Terry J. Reedy added the comment: Mark, this is a feature request to change the storage of loggers. A behavior issue (bug report) must report a discrepancy between doc and behavior. Vinay rejected that request as not really possible. Questions about using yum should go to a yum list or to py

[issue11950] logger use dict for loggers instead of WeakValueDictionary

Changes by Terry J. Reedy : -- versions: -Python 2.6, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue11950] logger use dict for loggers instead of WeakValueDictionary

Марк Коренберг added the comment: I'm not YUM developer, I'm very sad user of YUM API. Also, I'm novice in python logging complex system. 1. There is no way to remove logger once it added via getLogger(). why? 2. When yum should close handlers? In destructor (cleanup function) of module? 3. Wh

[issue11950] logger use dict for loggers instead of WeakValueDictionary

Vinay Sajip added the comment: I had to delete my previous response to the initial post, as something got mangled in it. Here's what I meant to say: -- It sounds to me as if there's a problem in yum that needs sorting out: I'm not sure why it would n

[issue11950] logger use dict for loggers instead of WeakValueDictionary

Changes by Vinay Sajip : -- Removed message: http://bugs.python.org/msg134786 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue11950] logger use dict for loggers instead of WeakValueDictionary

Vinay Sajip added the comment: It sounds to me as if there's a problem in yum that needs sorting out: I'm not sure why it would need dozens of loggers. As your workaround snippet shows, leaking files is not due to loggers but due to handlers - they're a different animal. Handlers need not be

[issue11950] logger use dict for loggers instead of WeakValueDictionary

New submission from Марк Коренберг : logger use dict for loggers instead of WeakValueDictionary Now, when object returned by getLogger() gets unreferenced - it will not be garbage collected, as reference is stored in logging module. This will results in leaked file object, that cannot be close