[issue8056] Piped parent's multiprocessing.Process children cannot write to stdout

Vojtech Fried added the comment: Thanks, the registry change proposed in the article fixed it. -- ___ Python tracker ___ ___ Python-bu

[issue8056] Piped parent's multiprocessing.Process children cannot write to stdout

Tim Golden added the comment: That's (still...) a known issue with Windows file associations and redirects: http://support.microsoft.com/kb/321788 In theory it was fixed way back when. In practise... On 30/06/2010 15:04, Vojtech Fried wrote: > > Vojtech Fried added the comment: > > I hav

[issue8056] Piped parent's multiprocessing.Process children cannot write to stdout

Vojtech Fried added the comment: I have the same problem. Not only for piping but also when using redirection, e.g. 'stdout.py > log.txt'. Interesting thing is that when I run it like 'python.exe stdout.py > log.txt' it works. I don't see why this should matter but apparently it does. ".py" f

[issue8056] Piped parent's multiprocessing.Process children cannot write to stdout

Vilnis Termanis added the comment: I tried to reproduce / narrow-down the cause of this with a debug build in a VM but couldn't reproduce the behaviour (neither with debug nor with standard 2.6.4 binary). I have to conclude that there is something perculiar with my native Windows installation

[issue8056] Piped parent's multiprocessing.Process children cannot write to stdout

New submission from Vilnis Termanis : Affects Win32 only (tested under Ubuntu 9.10-64 and XP-32 with v2.6.4). If script output is piped, child processes created via multiprocessing.Process cannot write to stdout. Also, trying to call stdout.flush() in child processes causes IOError. Normal be