summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Kluyver <takowl@gmail.com>2015-09-22 15:26:19 +0100
committerThomas Kluyver <takowl@gmail.com>2015-09-22 15:26:19 +0100
commitd937de283899dcf07efeaa5182ce1cccd615da55 (patch)
tree3068ff9f48779d57919a66abb15c6b4b42762c51
parenta8e0b19beb06500c5d92597a4a5b4e4e58ecc85b (diff)
parent3257ab3dad570a82133a99c8b69d8b8d3d6b7f2c (diff)
downloadpexpect-git-d937de283899dcf07efeaa5182ce1cccd615da55.tar.gz
Merge branch 'faq-pyte-redirect'
Conflicts: doc/FAQ.rst
-rw-r--r--doc/FAQ.rst15
1 files changed, 7 insertions, 8 deletions
diff --git a/doc/FAQ.rst b/doc/FAQ.rst
index 0636772..dc86c4f 100644
--- a/doc/FAQ.rst
+++ b/doc/FAQ.rst
@@ -117,14 +117,13 @@ another application.
**Q: Can I do screen scraping with this thing?**
A: That depends. If your application just does line-oriented output then
-this is easy. If it does screen-oriented output then it may work, but it
-could be hard. For example, trying to scrape data from the 'top' command
-would be hard. The top command repaints the text window.
-
-I am working on an ANSI / VT100 terminal emulator that will have methods
-to get characters from an arbitrary X,Y coordinate of the virtual screen.
-It works and you can play with it (see :mod:`pexpect.ANSI`), but I have
-no working examples at this time.
+this is easy. If a program emits many terminal sequences, from video
+attributes to screen addressing, such as programs using curses, then
+it may become very difficult to ascertain what text is displayed on a screen.
+
+We suggest using the `pyte <https://github.com/selectel/pyte>`_ library to
+screen-scrape. The module :mod:`pexpect.ANSI` released with previous versions
+of pexpect is now marked deprecated and may be removed in the future.
**Q: I get strange behavior with pexect and gevent**