Eryk Sun added the comment:
>if p.exitcode != 0:
>print('Child failed with exit code:', p.exitcode)
Interestingly the exit code is always 1 when running under pythonw.exe. I just
inspected what's going on by setting sys.stderr to a file and discovered the
following issue:
Fi
Eryk Sun added the comment:
Change the last print to test the exit code, as follows:
if p.exitcode != 0:
print('Child failed with exit code:', p.exitcode)
else:
print(num.value)
print(arr[:])
Note that when you fail to limit creating a new process to just the "__
Davin Potts added the comment:
I'm having difficulty watching your video attachment. Would it be possible to
instead describe, preferably with example code that others can similarly try to
reproduce the behavior, what you're experiencing?
Please keep in mind what the documentation repeatedly
New submission from Just a Person:
Lately, I have been having trouble using the multiprocessing library's shared
memory on Windows. Often, updating the .value property seems to fail for no
reason. As shown in the attached video, changing ```if __name__ ==
'__main__':``` in the sample code from
