Module: terminal.console.interactiveshell — IPython 2.3.1 documentation

### Navigation

- index
- modules |
- modules |
- next |
- previous |
- home|
- search|
- documentation »
- The IPython API »

# Module: `terminal.console.interactiveshell`

terminal client to the IPython kernel

## 1 Class

class `IPython.terminal.console.interactiveshell.` `ZMQTerminalInteractiveShell`(config=None, ipython_dir=None, profile_dir=None, user_ns=None, user_module=None, custom_exceptions=((), None), usage=None, banner1=None, banner2=None, display_banner=None, **kwargs)

  Bases: `IPython.terminal.interactiveshell.TerminalInteractiveShell`

  A subclass of TerminalInteractiveShell that uses the 0MQ kernel

  `handle_iopub`(msg_id='')

    Process messages on the IOPub channel

    This method consumes and processes messages on the IOPub channel, such as stdout, stderr, pyout and status.

    It only displays output that is caused by this session.

  `handle_stdin_request`(msg_id, timeout=0.1)

    Method to capture raw_input

  `init_completer`()

    Initialize the completion machinery.

    This creates completion machinery that can be used by client code, either interactively in-process (typically triggered by the readline library), programmatically (such as in test suites) or out-of-process (typically over the network by remote frontends).

  `interact`(display_banner=None)

    Closely emulate the interactive Python console.

  `run_cell`(cell, store_history=True)

    Run a complete IPython cell.

    Parameters: | cell : str The code (including IPython code such as %magic functions) to run. store_history : bool If True, the raw and translated cell will be stored in IPython’s history. For user code calling back into IPython’s machinery, this should be set to False.

  `wait_for_kernel`(timeout=None)

    method to wait for a kernel to be ready

### Navigation

- index
- modules |
- modules |
- next |
- previous |
- home|
- search|
- documentation »
- The IPython API »