Workers Should Not Inherit Your Logging Handlers
python
dev.to
Have you ever watched pool.join() sit there after a logging cleanup that looked boring in review? The workers are not crunching data. They are waiting on a lock the parent copied into them, or they are writing nowhere because the child never got a handler at all. That split is the whole story. Fork and spawn do not share a logging world. A free coding model will still offer you one setup_logging() import and call it tidy. The hang is a lock, not a slow map Stdlib logging wraps every