Python XMPP (Jabber) Library that Implements Everything as a Plugin
slixmpp is an MIT licensed XMPP library for Python.
The goals of the project are ease of implementation, and complete draft XEP (XMPP Extended Protocol) coverage.
Ideally the community will be able to use this for bots, easy XEP protocolling, etc.
- Sources inherited from project devel:languages:python
- Devel package for openSUSE:Factory
-
1
derived packages
- Links to openSUSE:Factory / python-slixmpp
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:smarty12:Python/python-slixmpp && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000124 124 Bytes | |
python-slixmpp.changes | 0000009859 9.63 KB | |
python-slixmpp.spec | 0000002164 2.11 KB | |
slixmpp-fix-legacyauth.patch | 0000000564 564 Bytes | |
slixmpp-slix-1.8.2.tar.bz2 | 0000503476 492 KB |
Revision 18 (latest revision is 23)
- Update to version 1.8.2 - Improve error handling for certificate errors - Add an XEP-0454 implementation (OMEMO Media sharing) - Fix support for RFC 3920 sessions - Update to version 1.8.1 * Fix a mypy issue, a test issue, and do not enable defusedxml unless explicitly asked. - Update to version 1.8.0 * The most important part of this release is that it fixes compatibility with python 3.10, but there are also plenty of changes and bugfixes! Many XEPs have been modified to accomodate an internal change, and as a result their public APIs have been modified. Slixmpp has an "internal API" for plugins, inherited from SleekXMPP which allows users of the library to substitute internal functions with their own, in order to e.g. provide a different storage backend (many default to in-memory), etc. This API has always been synchronous, which is not ideal in an asyncio library, and puts huge limits on what is possible to do. This change makes it possible to use async functions with the internal API, and as a result it forces us to change XEPs using this API to async in the relevant methods. As a rule of thumb, thin wrappers around del/set are generally preserved and return a future to guarantee that the task is done, while getters (which would require awaiting anyway when returning a future) are now pure coroutines. This inconsistency is a tradeoff to prevent wider changes across slixmpp internals and programs using it. - XEP-0012, Last Activity: - `begin_idle`, `end_idle`, `start_uptime`, `set_last_activity`, `del_last_activity` now return futures. - XEP-0027: GPG - `get_keyids` and `get_keyid` are now coroutines. - `set_keyid` and `del_keyid` now return a Future.
Comments 0