[issue8094] Multiprocessing infinite loop

2015-02-10 Thread Davin Potts
Changes by Davin Potts : -- stage: needs patch -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue8094] Multiprocessing infinite loop

2015-01-29 Thread Davin Potts
Davin Potts added the comment: On Windows 7 (64-bit), it was not possible to reproduce any infinite looping behavior with the supplied example code. Specifically, with the two examples from Benjamin, the observed behavior when running them was the same under 2.7.8 and default (3.5): a Runtime

[issue8094] Multiprocessing infinite loop

2013-02-01 Thread Philip Thiem
Philip Thiem added the comment: Actually sorry, now that I reread the details a second time, I'm not sure that is this the same deal. I'll just file a separate bug. -- ___ Python tracker __

[issue8094] Multiprocessing infinite loop

2013-02-01 Thread Philip Thiem
Philip Thiem added the comment: As an alternative, see http://bugs.python.org/issue10845 It contains a patch for the 3.X series which fixes the infinity loop. Applying it to the 2.X series will fix the issue and make a change the documentation unnecessary. -- nosy: +pthiem __

[issue8094] Multiprocessing infinite loop

2011-04-20 Thread R. David Murray
R. David Murray added the comment: Your code doesn't appear to have anything to do with the reported bug, which is about an infinite loop. But FYI to my understanding your script can't work on windows, since foo can't be imported. On linux, foo doesn't need to be imported. --

[issue8094] Multiprocessing infinite loop

2011-04-20 Thread Darren Dale
Darren Dale added the comment: I think I have a similar situation: C:\Py\Scripts\foo --- if __name__ == '__main__': import bar bar.main() C:\Py\Lib\site-packages\bar.py --- from multiprocessing import Pool def task(arg): return arg def main(): pool = Pool() res = pool.app

[issue8094] Multiprocessing infinite loop

2011-04-10 Thread Rodrigue Alcazar
Rodrigue Alcazar added the comment: I have tried to clearly state that the main module is imported by a newly created process. I have also added a comment explaining that an infinite loop like the one Benjamin describes could be created. -- keywords: +patch nosy: +Rodrigue.Alcazar Add

[issue8094] Multiprocessing infinite loop

2010-10-05 Thread Ask Solem
Changes by Ask Solem : -- nosy: +asksol ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue8094] Multiprocessing infinite loop

2010-03-09 Thread R. David Murray
Changes by R. David Murray : -- components: +Documentation -Library (Lib) priority: -> normal stage: -> needs patch type: crash -> behavior versions: +Python 2.6, Python 2.7, Python 3.2 ___ Python tracker

[issue8094] Multiprocessing infinite loop

2010-03-09 Thread R. David Murray
R. David Murray added the comment: Are you running this on windows? -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-li

[issue8094] Multiprocessing infinite loop

2010-03-09 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: The restriction that imposes the "__name__= '__main__'" idiom also applies when multiprocessing is not used in the main module. Actually the main module is always reloaded in the subprocess. The docs should be more explicit about it. -- assign

[issue8094] Multiprocessing infinite loop

2010-03-09 Thread Benjamin VENELLE
Benjamin VENELLE added the comment: Sorry I've not made clear my working platform. Yes, I'm running Python 3.1.1 32 bit on a Windows 7 x64. -- ___ Python tracker ___ ___

[issue8094] Multiprocessing infinite loop

2010-03-09 Thread Benjamin VENELLE
New submission from Benjamin VENELLE : Hi, The following code results in an infinite loop --> # import multiprocessing def f(m): print(m) p = multiprocessing.Process(target=f, args=('pouet',)) p.start() # I've firstly think about an issue in my code when Python loads this m