Python STOMP client
https://github.com/jasonrbriggs/stomp.py
A Python client library for accessing messaging servers (such as ActiveMQ, Apollo or RabbitMQ) using the STOMP protocol versions 1.0, 1.1 and 1.2. It can also be run as a standalone, command-line client for testing.
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/python-stomp.py && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| python-stomp.py.changes | 0000002615 2.55 KB | |
| python-stomp.py.spec | 0000001699 1.66 KB | |
| stomp.py-5.0.0.tar.gz | 0000053715 52.5 KB |
Revision 5 (latest revision is 13)
Dominique Leuenberger (dimstar_suse)
accepted
request 761142
from
Tomáš Chvátal (scarabeus_iv)
(revision 5)
- dropped Python 2 support, not supported by the package - update to version 5.0.0: * Fix for credentials exposure (https://github.com/jasonrbriggs/stomp.py/pull/244) * Check for ``STOMP_SKIP_HOSTNAME_SCAN`` environment variable before extending ``LOCALHOST_NAMES`` * Remove python2 backwards compatibility * Update dockerfile for better local testing * Fix docker and travis setup, so there are consistent builds both locally and via CI * Drop deprecated start/stop methods from connection (issue https://github.com/jasonrbriggs/stomp.py/issues/257) * Fix for missing return in get_ssl (https://github.com/jasonrbriggs/stomp.py/pull/258) * Clear heartbeat event after heartbeat loop ends (https://github.com/jasonrbriggs/stomp.py/pull/260) * Update listener to move receive/message_received/heartbeat_received vars inside the 'with' blocks (https://github.com/jasonrbriggs/stomp.py/pull/252) * Simplify logging calls * Tidy up listeners (correct the behaviour of TestListener) * Fix problem with double-disconnect notification (ihttps://github.com/jasonrbriggs/stomp.py/issues/245) * Add facility for PrintingListener to write to log rather than print statements
Comments 0