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`.`web`.`error`.`UnsupportedMethod``

exception documentation

`class UnsupportedMethod(Exception): (source)`

View In Hierarchy

Raised by a resource when faced with a strange request method.

RFC 2616 (HTTP 1.1) gives us two choices when faced with this situation: If the type of request is known to us, but not allowed for the requested resource, respond with NOT_ALLOWED. Otherwise, if the request is something we don't know how to deal with in any case, respond with NOT_IMPLEMENTED.

When this exception is raised by a Resource's render method, the server will make the appropriate response.

This exception's first argument MUST be a sequence of the methods the resource *does* support.

Method | `__init__` | Undocumented
Method | `__str__` | Undocumented
Instance Variable | `allowedMethods` | Undocumented

def __init__(self, allowedMethods, *args): (source)

Undocumented

def __str__(self): (source)

Undocumented

Returns
`str` | Undocumented

allowedMethods = (source)

Undocumented