stanza — XSOs for dealing with stanzas¶
This module provides XSO subclasses which provide access to stanzas and their RFC6120-defined child elements.
Much of what you’ll read here makes much more sense if you have read RFC 6120.
Top-level classes¶
- class aioxmpp.stanza.StanzaBase(*[, from_][, to][, id_])[source]¶
Base for all stanza classes. Usually, you will use the derived classes:
Message An XMPP message stanza. Presence An XMPP presence stanza. IQ An XMPP IQ stanza. However, some common attributes are defined in this base class:
- lang¶
The xml:lang value as LanguageTag.
Note
The id_ attribute is not defined in StanzaBase as different stanza classes have different requirements with respect to presence of that attribute.
In addition to these attributes, common methods needed are also provided:
- autoset_id()[source]¶
If the id_ already has a non-false (false is also the empty string!) value, this method is a no-op.
Otherwise, the id_ attribute is filled with eight bytes of random data, encoded as base64.
Note
This method only works on subclasses of StanzaBase which define the id_ attribute.
- make_error(error)[source]¶
Create a new instance of this stanza (this directly uses type(self), so also works for subclasses without extra care) which has the given error value set as error.
In addition, the id_, from_ and to values are transferred from the original (with from and to being swapped). Also, the type_ is set to "error".
- class aioxmpp.Message(*[, from_][, to][, id_][, type_])¶
An XMPP message stanza. The keyword arguments can be used to initialize the attributes of the Message.
- id_¶
The optional ID of the stanza.
- type_¶
The type attribute of the stanza. The allowed values are enumerated in MessageType.
Changed in version 0.7: Starting with 0.7, the enumeration MessageType is used. Before, strings equal to the XML attribute value character data were used ("chat", "headline", and so on).
As of 0.7, setting the string equivalents is still supported. However, reading from the attribute always returns the corresponding enumeration members (which still compare equal to their string equivalents).
Deprecated since version 0.7: The use of the aforementioned string values is deprecated and will lead to TypeError and/or ValueError being raised when they are written to this attribute. See the Changelog for Version 0.7 for further details on how to upgrade your code efficiently.
- body¶
A LanguageMap mapping the languages of the different body elements to their text.
Changed in version 0.5: Before 0.5, this was a XSOList.
- subject¶
A LanguageMap mapping the languages of the different subject elements to their text.
Changed in version 0.5: Before 0.5, this was a XSOList.
- thread¶
A Thread instance representing the threading information attached to the message or None if no threading information is attached.
Note that some attributes are inherited from StanzaBase:
from_ sender JID to recipient JID lang xml:lang value error Error instance
- class aioxmpp.IQ(*[, from_][, to][, id_][, type_])¶
An XMPP IQ stanza. The keyword arguments can be used to initialize the attributes of the IQ.
- id_¶
The optional ID of the stanza.
- type_¶
The type attribute of the stanza. The allowed values are enumerated in IQType.
Changed in version 0.7: Starting with 0.7, the enumeration IQType is used. Before, strings equal to the XML attribute value character data were used ("get", "set", and so on).
As of 0.7, setting the string equivalents is still supported. However, reading from the attribute always returns the corresponding enumeration members (which still compare equal to their string equivalents).
Deprecated since version 0.7: The use of the aforementioned string values is deprecated and will lead to TypeError and/or ValueError being raised when they are written to this attribute. See the Changelog for Version 0.7 for further details on how to upgrade your code efficiently.
- payload¶
An XSO which forms the payload of the IQ stanza.
Note that some attributes are inherited from StanzaBase:
from_ sender JID to recipient JID lang xml:lang value error Error instance New payload classes can be registered using:
- class aioxmpp.Presence(*[, from_][, to][, id_][, type_])¶
An XMPP presence stanza. The keyword arguments can be used to initialize the attributes of the Presence.
- id_¶
The optional ID of the stanza.
- type_¶
The type attribute of the stanza. The allowed values are enumerated in PresenceType.
Changed in version 0.7: Starting with 0.7, the enumeration PresenceType is used. Before, strings equal to the XML attribute value character data were used ("probe", "unavailable", and so on, as well as None to indicate the absence of the attribute and thus “available” presence).
As of 0.7, setting the string equivalents and None is still supported. However, reading from the attribute always returns the corresponding enumeration members (which still compare equal to their string equivalents).
Deprecated since version 0.7: The use of the aforementioned string values (and None) is deprecated and will lead to TypeError and/or ValueError being raised when they are written to this attribute. See the Changelog for Version 0.7 for further details on how to upgrade your code efficiently.
- priority¶
The priority value of the presence. The default here is 0 and corresponds to an absent priority element.
- status¶
A LanguageMap mapping the languages of the different status elements to their text.
Changed in version 0.5: Before 0.5, this was a XSOList.
Note that some attributes are inherited from StanzaBase:
from_ sender JID to recipient JID lang xml:lang value error Error instance
Payload classes¶
For Presence and Message as well as IQ errors, the standardized payloads also have classes which are used as values for the attributes:
- class aioxmpp.stanza.Error(*[, condition][, type_][, text])[source]¶
An XMPP stanza error. The keyword arguments can be used to initialize the attributes of the Error.
- type_¶
The type attribute of the stanza. The allowed values are enumerated in ErrorType.
Changed in version 0.7: Starting with 0.7, the enumeration ErrorType is used. Before, strings equal to the XML attribute value character data were used ("cancel", "auth", and so on).
As of 0.7, setting the string equivalents is still supported. However, reading from the attribute always returns the corresponding enumeration members (which still compare equal to their string equivalents).
Deprecated since version 0.7: The use of the aforementioned string values is deprecated and will lead to TypeError and/or ValueError being raised when they are written to this attribute. See the Changelog for Version 0.7 for further details on how to upgrade your code efficiently.
- condition¶
The standard defined condition which triggered the error. Possible values can be determined by looking at the RFC or the source.
Any child elements unknown to the XSO are dropped. This is to support application-specific conditions used by other applications. To register your own use xso.XSO.register_child() on application_condition:
- application_condition¶
A xso.XSO.Child which can be used to register support for application-specific errors.
To register a class as application condition, use:
- classmethod as_application_condition(other_cls)[source]¶
Register other_cls as child class for the application_condition attribute. Doing so will allows the class to be parsed instead of being discarded.
See also
make_application_error() — creates and automatically registers a new application error condition.
- aioxmpp.stanza.make_application_error(name, tag)[source]¶
Create and return a class inheriting from xso.XSO. The xso.XSO.TAG is set to tag and the class’ name will be name.
In addition, the class is automatically registered with Error.application_condition using as_application_condition().
Keep in mind that if you subclass the class returned by this function, the subclass is not registered with Error. In addition, if you do not override the TAG, you will not be able to register the subclass as application defined condition as it has the same tag as the class returned by this function, which has already been registered as application condition.
For messages¶
- class aioxmpp.stanza.Thread[source]¶
Threading information, consisting of a thread identifier and an optional parent thread identifier.
- identifier¶
Identifier of the thread
- class aioxmpp.stanza.Subject[source]¶
The subject of a Message stanza.
While it might seem intuitive to refer to the subject using a ChildText descriptor, the fact that there might be multiple texts for different languages justifies the use of a separate class.
- lang¶
The xml:lang of this subject part, as LanguageTag.
- text¶
The textual content of the subject
- class aioxmpp.stanza.Body[source]¶
The textual body of a Message stanza.
While it might seem intuitive to refer to the body using a ChildText descriptor, the fact that there might be multiple texts for different languages justifies the use of a separate class.
- lang¶
The xml:lang of this body part, as LanguageTag.
- text¶
The textual content of the body.
For presence’¶
- class aioxmpp.stanza.Status[source]¶
The status of a Presence stanza.
While it might seem intuitive to refer to the status using a ChildText descriptor, the fact that there might be multiple texts for different languages justifies the use of a separate class.
- lang¶
The xml:lang of this status part, as LanguageTag.
- text¶
The textual content of the status
Exceptions¶
- class aioxmpp.stanza.PayloadError(msg, partial_obj, ev_args, descriptor)[source]¶
Base class for exceptions raised when stanza payloads cannot be processed.
This is a subclass of StanzaError. partial_obj has the additional guarantee that the attributes StanzaBase.from_, StanzaBase.to, StanzaBase.type_ and StanzaBase.id_ are already parsed completely.
- class aioxmpp.stanza.PayloadParsingError(partial_obj, ev_args, descriptor)[source]¶
A constraint of a sub-object was not fulfilled and the stanza being processed is illegal. The partially parsed stanza object is provided in partial_obj.
This is a subclass of PayloadError.