[issue26633] multiprocessing behavior combining daemon with non-daemon children inconsistent with threading

2016-03-29 Thread Robert Cope
Changes by Robert Cope : -- nosy: +rpcope1 ___ Python tracker ___ ___ Python-bugs-list

[issue26633] multiprocessing behavior combining daemon with non-daemon children inconsistent with threading

2016-03-28 Thread Davin Potts
Changes by Davin Potts : -- nosy: +davin ___ Python tracker ___ ___

[issue26633] multiprocessing behavior combining daemon with non-daemon children inconsistent with threading

2016-03-24 Thread SilentGhost
Changes by SilentGhost : -- nosy: +jnoller, sbt ___ Python tracker ___ ___

[issue26633] multiprocessing behavior combining daemon with non-daemon children inconsistent with threading

2016-03-23 Thread Josh Rosenberg
Josh Rosenberg added the comment: Oops, left the info log in my replacement code for the non-daemon case outside the if not daemon: block; it should be inside (since it's not joining the daemon threads). -- ___ Python tracker

[issue26633] multiprocessing behavior combining daemon with non-daemon children inconsistent with threading

2016-03-23 Thread Josh Rosenberg
New submission from Josh Rosenberg: Unclear if this is just unclear docs, or incorrect behavior. Per this Stack Overflow question ( https://stackoverflow.com/questions/36191447/why-doesnt-the-daemon-program-exit-without-join ), you get some rather odd behavior when you have both daemon and