Go to the latest version of this document.
search in docstrings

Search bar offers the following options:

- Term presence. The below example searches for documents that must contain “foo”, might contain “bar” and must not contain “baz”: `+foo bar -baz`
- Wildcards. The below example searches for documents with words beginning with “foo”: `foo*`
- Search in specific fields. The following search matches all objects in "twisted.mail" that matches “search”: `+qname:twisted.mail.* +search`

  Possible fields: 'name', 'qname' (fully qualified name), 'docstring', and 'kind'. Last two fields are only applicable if "search in docstrings" is enabled.

- Fuzzy matches. The following search matches all documents that have a word within 1 edit distance of “foo”: `foo~1`

Results provided by Lunr.js

# ``twisted`.`internet`.`interfaces`.`_ISupportsExitSignalCapturing``

interface documentation

`class _ISupportsExitSignalCapturing(Interface): (source)`

Known implementations: `twisted.internet.base.ReactorBase`

View In Hierarchy

An implementor of `_ISupportsExitSignalCapturing` will capture the value of any delivered exit signal (SIGINT, SIGTERM, SIGBREAK) for which it has installed a handler. The caught signal number is made available in the _exitSignal attribute.

Attribute | `_exitSignal` | `int` or `None`, the integer exit signal delivered to the application, or None if no signal was delivered.

_exitSignal = (source)

`int` or `None`, the integer exit signal delivered to the application, or None if no signal was delivered.