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`.`protocols`.`amp`.`_CommandLocatorMeta``

class documentation

`class _CommandLocatorMeta(type): (source)`

View In Hierarchy

This metaclass keeps track of all of the Command.responder-decorated methods defined since the last CommandLocator subclass was defined. It assumes (usually correctly, but unfortunately not necessarily so) that those commands responders were all declared as methods of the class being defined. Note that this list can be incorrect if users use the Command.responder decorator outside the context of a CommandLocator class declaration.

Command responders defined on subclasses are given precedence over those inherited from a base class.

The Command.responder decorator explicitly cooperates with this metaclass.

Method | `__new__` | Undocumented
Class Variable | `_currentClassCommands` | Undocumented

def __new__(cls, name, bases, attrs): (source)

Undocumented

_currentClassCommands: `List[Tuple[Command, Callable]]` = (source)

Undocumented