Denver Coneybeare <denver.coneybe...@gmail.com> added the comment:

I just re-tested this in cpython trunk at changeset and the issue does not 
appear to be reproducible.

I first launched IDLE by running "python lib\idlelib\idle.py".  Then I entered 
the following:

Python 3.3a0 (default, Apr  2 2011, 21:55:40) [MSC v.1500 32 bit (Intel)] on 
win32
Type "copyright", "credits" or "license()" for more information.
>>> import sys
>>> sys.getwindowsversion()
sys.getwindowsversion(major=5, minor=1, build=2600, platform=2, 
service_pack='Service Pack 3')
>>> import subprocess
>>> PIPE = subprocess.PIPE
>>> p = subprocess.Popen(["python", "-c", "print(32)"], stdin=None, 
>>> stdout=PIPE, stderr=PIPE)
>>> p
<subprocess.Popen object at 0x00F85610>
>>> p.returncode
>>>

Popen() did not raise any exceptions.  I also tried in Python 2.7 and the Popen 
called succeeded there as well.  So my inability to reproduce the issue does 
not necessarily mean that the issue is fixed, but rather that it is likely 
dependent on the version of Windows on which Python is running.

That being said, the linked issue issue1124861 logs what appears to be the same 
issue and it was fixed in Python 2.6.  So maybe I'm just not old enough to have 
encountered this issue :)  Anyways, this issue probably can be closed as either 
a duplicate or fixed incidentally.

----------
nosy: +denversc

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue3905>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to