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`.`trial`.`_dist`.`disttrial`.`WorkerPoolConfig``

class documentation

`class WorkerPoolConfig: (source)`

View In Hierarchy

Configuration parameters for a pool of test-running workers.

Instance Variable | `logFile` | The basename of the overall test log file.
Instance Variable | `numWorkers` | The number of workers in the pool.
Instance Variable | `workerArguments` | Extra arguments to pass the worker process in its argv.
Instance Variable | `workingDirectory` | A directory in which working directories for each of the workers will be created.

logFile: `str` = (source)

The basename of the overall test log file.

numWorkers: `int` = (source)

The number of workers in the pool.

workerArguments: `Sequence[str]` = (source)

Extra arguments to pass the worker process in its argv.

workingDirectory: `FilePath[Any]` = (source)

A directory in which working directories for each of the workers will be created.