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”:
Search in specific fields. The following search matches all objects
in "twisted.mail" that matches “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”:
Results provided by Lunr.js
UNIX socket support for Twisted.
End users shouldn't use this module directly - use the reactor APIs instead.
Maintainer: Itamar Shtull-Trauring
||A client for Unix sockets.|
||A connected datagram UNIX socket.|
||Datagram UNIX port, listening for packets.|
||No class docstring; 0/4 instance variable, 2/6 methods, 1/1 class method documented|
||No class docstring; 0/2 instance variable, 0/3 method, 1/1 class method documented|
||Mixin for stream-oriented UNIX transports which uses sendmsg and recvmsg to offer additional functionality, such as copying file descriptors into other processes.|
||No class docstring; 1/1 method documented|
||Behaviorless placeholder used when twisted.python.sendmsg is not available, preventing
||Pack an integer into an ancillary data structure suitable for use with
||Determine whether the given unix socket path is in a filesystem namespace.|
Pack an integer into an ancillary data structure suitable for use with
Determine whether the given unix socket path is in a filesystem namespace.
While most PF_UNIX sockets are entries in the filesystem, Linux 2.2 and above support PF_UNIX sockets in an "abstract namespace" that does not correspond to any path. This function returns True if the given socket path is stored in the filesystem and False if the path is in this abstract namespace.