[issue25053] Possible race condition in Pool

Anil Bishnoie added the comment: Fatal Python error: init_sys_streams: can't initialize sys standard streams Python runtime state: core initialized File "C:\Python38\lib\multiprocessing\process.py", line 315, in _bootstrap During handling of the above exception, another exception occurred:

[issue25053] Possible race condition in Pool

Anil Bishnoie added the comment: Process SpawnPoolWorker-36: Process SpawnPoolWorker-28: Process SpawnPoolWorker-33: Process SpawnPoolWorker-30: Process SpawnPoolWorker-34: Process SpawnPoolWorker-32: Process SpawnPoolWorker-35: Process SpawnPoolWorker-38: Process SpawnPoolWorker-37: Process Sp

[issue25053] Possible race condition in Pool

Anil Bishnoie added the comment: from multiprocessing import Pool l_adt=ldir() l_ln=len(l_stk) p = Pool(processes=l_ln) df = p.map(ld_df1, [i for i in l_adt]) l_ln=12 processes Above is the self explanatory code snippet IS there a resolution ? -- ___

[issue25053] Possible race condition in Pool

Anil Bishnoie added the comment: Before running the Pool I checked whether my func existed in memory or not and it was there well defined by address and works fine otherwise >>> ld_df1 -- ___ Python tracker _

[issue25053] Possible race condition in Pool

Anil Bishnoie added the comment: Traceback (most recent call last): File "C:\Python38\lib\multiprocessing\process.py", line 315, in _bootstrap self.run() File "C:\Python38\lib\multiprocessing\process.py", line 108, in run self._target(*self._args, **self._kwargs) File "C:\Python38

[issue25053] Possible race condition in Pool

Anil Bishnoie added the comment: I still get this error while processing multiple tasks in python 3.8 Is this bug resolved and where I can find resolution ? -- nosy: +anilb versions: +Python 3.8 ___ Python tracker

[issue25053] Possible race condition in Pool

Stanislaw Izaak Pitucha added the comment: I agree with what you said mostly. I wonder though if the message could be clearer in the docs. I remember that the rule about the module being importable without side-effects, but didn't even consider that for the interactive session. If I understand

[issue25053] Possible race condition in Pool

Changes by Davin Potts : -- status: open -> pending versions: +Python 3.5 ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue25053] Possible race condition in Pool

Davin Potts added the comment: I have been able to reproduce the behavior you described under 3.5 under one set of circumstances so far. When attempting to use classes/functions/other not defined in an importable module, an AttributeError is expected as you observed. The viability of that ex

[issue25053] Possible race condition in Pool

New submission from Stanislaw Izaak Pitucha: This is something that happened once and I cannot reproduce anymore. In an IPython session I've done the following (see session below), which resulted in pool.map raising its internal exceptions in cases where it shouldn't. Then it worked again. (se