Documentation change: A simple sphinx extension has been added which auto-detects coroutines and adds a directive to mark up signals.
The latter has been added to relevant places and the former automatically improves the documentations quality.
aioxmpp.roster.Service now implements presence subscription management. To track the presence of peers, aioxmpp.presence has been added.
aioxmpp.stream and aioxmpp.stream_xsos are part of the public API now. aioxmpp.stream_xsos has gained the XSOs for SASL (previously in aioxmpp.sasl) and StartTLS (previously in aioxmpp.security_layer).
aioxmpp.xso.XSO subclasses now support copying and deepcopying.
aioxmpp.protocol has been moved into the internal API part.
aioxmpp.stanza.Message specification fixed to have "normal" as default for type_ and relax the unknown child policy.
Possibly breaking change: aioxmpp.xso.XSO.DECLARE_NS is now automatically generated by the meta class aioxmpp.xso.XMLStreamClass. See the documentation for the detailed rules.
To get the old behaviour for your class, you have to put DECLARE_NS = {} in its declaration.
aioxmpp.stream.StanzaStream has a positional, optional argument (local_jid) for ejabberd compatiblity.
Several fixes and workarounds, finally providing ejabberd compatibility:
Allow pinning of certificates for which no issuer certificate is available, because it is missing in the server-provided chain and not available in the local certificate store. This is, with respect to trust, treated equivalent to a self-signed cert.
Fix stream management state going out-of-sync when an errorneous stanza (unknown payload, type or validator errors on the payload) was received. In addition, IQ replies which cannot be processed raise aioxmpp.errors.ErrorneousStanza from aioxmpp.stream.StanzaStream.send_iq_and_wait_for_reply() and when registering futures for the response using aioxmpp.stream.StanzaStream.register_iq_response_future(). See the latter for details on the semantics.
Fixed a bug in aioxmpp.xml.XMPPXMLGenerator which would emit elements in the wrong namespace if the meaning of a XML namespace prefix was being changed at the same time an element was emitted using that namespace.
The defaults for unknown child and attribute policies on aioxmpp.xso.XSO are now DROP and not FAIL. This is for better compatibility with old implementations and future features.
Breaking change: The required keyword argument on most aioxmpp.xso descriptors has been removed. The semantics of the default keyword argument have been changed.
Before 0.3, the XML elements represented by descriptors were not required by default and had to be marked as required e.g. by setting required=True in xso.Attr constructor.
Since 0.3, the descriptors are generally required by default. However, the interface on how to change that is different. Attributes and text have a default keyword argument which may be set to a value (which may also be None). In that case, that value indicates that the attribute or text is absent: it is used if the attribute or text is missing in the source XML and if the attribute or text is set to the default value, it will not be emitted in XML.
Children do not support default values other than None; thus, they are simply controlled by a boolean flag required which needs to be passed to the constructor.
The class attributes SERVICE_BEFORE and SERVICE_AFTER have been renamed to ORDER_BEFORE and ORDER_AFTER respectively.
The aioxmpp.service.Service class has additional support to handle the old attributes, but will emit a DeprecationWarning if they are used on a class declaration.
See aioxmpp.service.Meta.SERVICE_AFTER for more information on the deprecation cycle of these attributes.