[issue24717] python logging handler not used when added after a process is started

Vinay Sajip added the comment: Context is crucial. The Python documentation is not wrong, but doesn't belabour the point that it refers to the most common, single-process case. The problem you encountered is not specific to logging: you need to understand all aspects of how forking works and h

[issue24717] python logging handler not used when added after a process is started

eric added the comment: The python documentation says that when one calls logger.getLogger with the same identifier that one gets the same instance of the logger. I would guess that in the case of a Process this is not the case. I would have to assume that the handlers attached to that Process

[issue24717] python logging handler not used when added after a process is started

Vinay Sajip added the comment: This is not a bug - it's how processes work on POSIX. Multiprocessing on POSIX generally uses the fork system call, which happens when you create a another process via the Process(...) call. At this point, the created process is a copy of the original process. Wh

[issue24717] python logging handler not used when added after a process is started

Changes by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue24717] python logging handler not used when added after a process is started

New submission from eric: If I have interpreted the python3 documentation correctly, regardless of where I add the handler to the root logger, my log messages from within a Process should be sent to a file. However, this is not the case. Here is a complete program which demonstrates the proble