[ python-Bugs-1539954 ] Closing a pipe can lead to uncompleted command

SourceForge.net noreply at sourceforge.net
Wed Aug 16 15:12:11 CEST 2006


Bugs item #1539954, was opened at 2006-08-14 14:11
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1539954&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Stefan Sonnenberg (sunmountain)
Assigned to: Nobody/Anonymous (nobody)
Summary: Closing a pipe can lead to uncompleted command

Initial Comment:
I'm using python version 
2.3.3 (#0, Apr 22 2004, 11:33:00) [SunCC 5.5]
under Solaris 9.

I'm doing basically this:

p = os.popen("cmd","w")
p.write(cmd_string)
p.close()

Sometimes the command opened with popen does not
work completely.
A explicit p.flush() is needed to get the desired
behaviour.



----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2006-08-16 15:12

Message:
Logged In: YES 
user_id=21627

I can't reproduce this, and I can't see anything in the
Python source code that might be causing it. Can you provide
a reproducable test case?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1539954&group_id=5470


More information about the Python-bugs-list mailing list