fdpexpect - use pexpect with a file descriptor¶
This is like pexpect, but it will work with any file descriptor that you pass it. You are reponsible for opening and close the file descriptor. This allows you to use Pexpect with sockets and named pipes (FIFOs).
- This license is approved by the OSI and FSF as GPL-compatible.
Copyright (c) 2012, Noah Spurrier <firstname.lastname@example.org> PERMISSION TO USE, COPY, MODIFY, AND/OR DISTRIBUTE THIS SOFTWARE FOR ANY PURPOSE WITH OR WITHOUT FEE IS HEREBY GRANTED, PROVIDED THAT THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE APPEAR IN ALL COPIES. THE SOFTWARE IS PROVIDED “AS IS” AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
- class pexpect.fdpexpect.fdspawn(fd, args=, timeout=30, maxread=2000, searchwindowsize=None, logfile=None)[source]¶
This is like pexpect.spawn but allows you to supply your own open file descriptor. For example, you could use it to read through a file looking for patterns, or to control a modem or serial device.
- __init__(fd, args=, timeout=30, maxread=2000, searchwindowsize=None, logfile=None)[source]¶
This takes a file descriptor (an int) or an object that support the fileno() method (returning an int). All Python file-like objects support fileno().
This checks if the file descriptor is still valid. If os.fstat() does not raise an exception then we assume it is alive.
Close the file descriptor.
Calling this method a second time does nothing, but if the file descriptor was closed elsewhere, OSError will be raised.
fdspawn inherits all of the methods of spawn, but not all of them can be used, especially if the file descriptor is not a terminal. Some methods may do nothing (e.g. kill()), while others will raise an exception (e.g. terminate()). This behaviour might be made more consistent in the future, so try to avoid relying on it.