summaryrefslogtreecommitdiff
path: root/doc/FAQ.rst
diff options
context:
space:
mode:
authorChris Merck <chrismerck@gmail.com>2014-02-20 10:47:26 -0500
committerChris Merck <chrismerck@gmail.com>2014-02-20 10:47:26 -0500
commit81c45250dd8d48c959e242064590567f627f28f7 (patch)
tree4329b97fec4b29bcfa328326f2cdd293921d6dfb /doc/FAQ.rst
parentd7be1bdc66df448fc055f8aa8da795224c7ce747 (diff)
downloadpexpect-git-81c45250dd8d48c959e242064590567f627f28f7.tar.gz
FAQ.rst: Removed redundant paragraph.
Diffstat (limited to 'doc/FAQ.rst')
-rw-r--r--doc/FAQ.rst15
1 files changed, 1 insertions, 14 deletions
diff --git a/doc/FAQ.rst b/doc/FAQ.rst
index 4230289..bec1c35 100644
--- a/doc/FAQ.rst
+++ b/doc/FAQ.rst
@@ -121,20 +121,7 @@ decides to change behavior based on whether it's a TTY or a block file
(see isatty()).
I hope that this qualifies as helpful. Don't use a pipe to control
-another application...
-
-Pexpect may seem similar to :func:`os.popen` or ``commands`` module. The
-main difference is that Pexpect (like Expect) uses a pseudo-TTY to talk
-to the child application. Most applications do not work well through the
-system() call or through pipes. And probably all applications that ask a
-user to type in a password will fail. These applications bypass the
-stdin and read directly from the TTY device. Many applications do not
-explicitly flush their output buffers. This causes deadlocks if you try
-to control an interactive application using a pipe. What happens is that
-most UNIX applications use the stdio (``#include <stdio.h>``) for input
-and output. The stdio library behaves differently depending on where the
-output is going. There is no way to control this behavior from the
-client end.
+another application.
**Q: Can I do screen scraping with this thing?**