[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

Change by Ethan Furman : -- nosy: +ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

luke_16 added the comment: Regarding Davin's last paragraph: "Without pulling apart your code...", I would like to point out that what I'm doing is what the Documentation instructs: https://docs.python.org/2/library/multiprocessing.html#using-a-remote-manager So, I want to access a process

[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

luke_16 added the comment: Relating to the idea that it is not recommended to spawn a process whenever there are already spawned threads running, which would be the case of the server side of my example, I have to disagree. If a process is supposed to be completely independent of the current

[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

Davin Potts added the comment: There are too many things going on in this example -- it would be far easier to digest if the example could be simplified. The general programming rule of thumb (completely unrelated to but still just as relevant to Python) that I think David might have been

[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

R. David Murray added the comment: My understanding is that the basic rule of thumb is: don't mix threads and multiprocessing. You may find that if you use spawn, it won't ever work. But I haven't used multiprocessing myself. -- nosy: +r.david.murray type: crash -> behavior

[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

New submission from Luciano Dionisio: After spending a lot of time trying to understand why my code will not execute as expected and after not getting any help from StackOverflow: