Hi Sander, My guess is that the two shell options must be treating the command string differently, thus the "|" sign has different functionalities on them.
Thanks! Shawn -----Original Message----- From: Sander Sweers [mailto:[email protected]] Sent: Monday, July 06, 2009 10:23 AM To: hyou Cc: Python Tutor List Subject: Re: [Tutor] Popen problem with a pipe sign "|" 2009/7/6 hyou <[email protected]>: > Do I post to the list by also replying to Python Tutor List? Yes, thanks. > Thanks for the answer! I found the problem was because I put the 2nd > argument to Popen with Shell = true. Though I'm not sure why it doesn't work > with Shell = true while the same setting works for other commands. You can read up on subprocess on [1]. I do not understand why this does not work with shell=True. My best guess is that it gets interpreted as a pipe. Greets Sander [1] http://docs.python.org/library/subprocess.html _______________________________________________ Tutor maillist - [email protected] http://mail.python.org/mailman/listinfo/tutor
