Issue1453

import os
(_, handle, child_stderr) = os.popen3("dir")
print child_stderr.read()

import subprocess
p = subprocess.Popen("dir", shell=True, stdin=subprocess.PIPE,
stdout=subprocess.PIPE, stderr=subprocess.PIPE)
(handle, child_stderr) = (p.stdout, p.stderr)
print child_stderr.read()

Seems i need to use:
import subprocess
p = subprocess.Popen("dir", shell=True, stdin=subprocess.PIPE,
stdout=subprocess.PIPE, stderr=subprocess.PIPE)
(handle, child_stderr) = p.communicate()
print child_stderr

I was able to reproduce this on Windows XP Java 6. Seems due to Java 
Windows process handling weirdness as it doesn't happen on POSIX. I'm 
not sure there's much we can do about it, Jython 2.2 did it too

As Simon points out people should be using subprocess instead anyway -- 
particularly since os.popen3 is eventually going away

Cannot reproduce on Windows 8.1 running on Java 7.

Looks like another early JDK process management issue, so closing this out.