83dbf21ba7
Launch a subprocess in a pseudo terminal (pty), and interact with both the process and its pty. Sometimes, piping stdin and stdout is not enough. There might be a password prompt that doesn’t read from stdin, output that changes when it’s going to a pipe rather than a terminal, or curses-style interfaces that rely on a terminal. If you need to automate these things, running the process in a pseudo terminal (pty) is the answer.
14 lines
524 B
Text
14 lines
524 B
Text
@comment $NetBSD: PLIST,v 1.1 2017/04/23 03:48:20 markd Exp $
|
|
${PYSITELIB}/${EGG_FILE}
|
|
${PYSITELIB}/ptyprocess/__init__.py
|
|
${PYSITELIB}/ptyprocess/__init__.pyc
|
|
${PYSITELIB}/ptyprocess/__init__.pyo
|
|
${PYSITELIB}/ptyprocess/_fork_pty.py
|
|
${PYSITELIB}/ptyprocess/_fork_pty.pyc
|
|
${PYSITELIB}/ptyprocess/_fork_pty.pyo
|
|
${PYSITELIB}/ptyprocess/ptyprocess.py
|
|
${PYSITELIB}/ptyprocess/ptyprocess.pyc
|
|
${PYSITELIB}/ptyprocess/ptyprocess.pyo
|
|
${PYSITELIB}/ptyprocess/util.py
|
|
${PYSITELIB}/ptyprocess/util.pyc
|
|
${PYSITELIB}/ptyprocess/util.pyo
|