[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Tim Golden added the comment: I can't reproduce either on 2.7 or on 3.5 with any of the examples shown. Closing again as not-a-bug. -- resolution: -> not a bug status: open -> closed versions: -Python 2.7, Python 3.4 ___ Python tracker

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Terry J. Reedy added the comment: That has been pointed out to me. I need to repost with the results after correcting the commands (there is still a problem). -- ___ Python tracker _

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

akira added the comment: > ID>>> s.check_output("pyflakes c:\programs\python34\lib\turtle.py") > hangs indefinitely, no output It might be unrelated to the issue but "\t" is a tab; a raw-string literal should be used instead: >>> from subprocess import check_output >>> check_output(r"pyfla

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Changes by Terry J. Reedy : -- nosy: +sahutd ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Terry J. Reedy added the comment: There are certainly some problems with subprocess on Windows. Note .../python34> pip pyflakes installs in a second or two. ...> pyflakes -h # Windows Command Propmpt WCP >>> import subprocess as s; s.check_output("pyflakes -h") console interpreter CI or Idle, a

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Patrick Gansterer added the comment: I can reproduce this on WinXP with 2.5, 2.7 and 3.2. On my other box (Win7 64bit) the same code works without problems. This problem happens only when I make a subprocess.call() to executables from my msysgit installation (e.g. echo, git). A call to 'notepa

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Brian Curtin added the comment: I'm with Tim and Mark - can't reproduce this, so I'm closing the report. If you are able to find another case which can reproduce this, feel free to re-open. -- resolution: -> rejected stage: -> committed/rejected status: open -> closed type: crash ->

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Alex Quinn added the comment: I am on Windows 7. I realized the "echo" command I'm piping to belongs to Cygwin. I'll try to make a different example to either support this, or otherwise close the bug. Thanks! -- ___ Python tracker

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Tim Golden added the comment: I can't reproduce on W7. Strangely, though, although my banner suggests that I have exactly the same build as you, I get a "\r\n" at the end of the communicate bytestream, not a simple "\n" as you're getting. Do you have any environment variables or Python comman

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

Mark Lawrence added the comment: I can't reproduce this using Windows Vista. -- nosy: +BreamoreBoy, brian.curtin, tim.golden ___ Python tracker ___ __

[issue8631] subprocess.Popen.communicate(...) hangs on Windows

New submission from Alex Quinn : After using subprocess.Popen(...).communicate(), the session hangs. c:\>python31 Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> from subprocess impo