[issue1452] subprocess's popen.stdout.seek(0) doesn't raise an error

Antoine Pitrou added the comment: Looks like it's a platform bug, nothing Python can do about. -- nosy: +pitrou resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue1452] subprocess's popen.stdout.seek(0) doesn't raise an error

Mark Lawrence added the comment: @Brian/Tim what would you expect to happen here? -- nosy: +BreamoreBoy, brian.curtin, tim.golden ___ Python tracker ___ _

[issue1452] subprocess's popen.stdout.seek(0) doesn't raise an error

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue1452] subprocess's popen.stdout.seek(0) doesn't raise an error

Changes by Alexander Belopolsky : -- type: -> feature request versions: +Python 3.2 -Python 3.0 ___ Python tracker ___ ___ Python-bugs

[issue1452] subprocess's popen.stdout.seek(0) doesn't raise an error

Changes by Christian Heimes: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue1452] subprocess's popen.stdout.seek(0) doesn't raise an error

Amaury Forgeot d'Arc added the comment: Python 2.5 on Windows has the same behaviour, it does not fail. In general, python does not try to hide this kind of differences. -- nosy: +amaury.forgeotdarc __ Tracker <[EMAIL PROTECTED]>

[issue1452] subprocess's popen.stdout.seek(0) doesn't raise an error

New submission from Christian Heimes: On Linux: >>> p = subprocess.Popen("ls", stdout=subprocess.PIPE) >>> p.stdout.read() b'...' >>> p.stdout.seek(0) Traceback (most recent call last): File "", line 1, in File "/home/heimes/dev/python/py3k/Lib/io.py", line 809, in seek pos = self.raw.s