diff options
| author | Thomas Kluyver <takowl@gmail.com> | 2015-09-21 19:56:19 +0100 |
|---|---|---|
| committer | Thomas Kluyver <takowl@gmail.com> | 2015-09-21 19:56:19 +0100 |
| commit | 944675a22ccedfda2ad8bad4ca4b852d5952883e (patch) | |
| tree | ab17e03a6df68e34c278c666e99ba0c2cb3d9442 | |
| parent | 29115334d6f8b770fd379bfd83bf339b26e00b82 (diff) | |
| parent | c8cd9c626cd4641d558c9da266fd2aa058d8e1db (diff) | |
| download | pexpect-944675a22ccedfda2ad8bad4ca4b852d5952883e.tar.gz | |
Merge pull request #255 from pexpect/faq-about-gevent
add FAQ entry about gevent, recommend isolation
| -rw-r--r-- | doc/FAQ.rst | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/FAQ.rst b/doc/FAQ.rst index bec1c35..33459b9 100644 --- a/doc/FAQ.rst +++ b/doc/FAQ.rst @@ -134,3 +134,11 @@ 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. + +**Q: I get strange behavior with pexect and gevent** + +A: Pexpect uses fork(2), exec(2), select(2), waitpid(2), and implements its +own selector in expect family of calls. pexpect has been known to misbehave +when paired with gevent. A solution might be to isolate your pexpect +dependent code from any frameworks that manipulate event selection behavior +by running it in an another process entirely. |