Eventbus
A library for dealing with getting arbitrary events moving throughout the system
Changelog
3.17
Add the ebosia.sync.start_pump function
This function will continually push events into the eventbus at a steady interval to ensure that the connection stays alive. This is to fight Docker Swarm’s VIP policy that closes down connections with no data traveling across them
3.16
Loosen up requirements for dev dependencies
3.15
Update to our own aioamqp to get the fix we need for disconnection errors in Python 3.5
3.14 & 3.13 & 3.12
Attempt to bypass a problem with aioamqp https://github.com/Polyconseil/aioamqp/issues/139
3.11
Don’t use release 3.10, it will never ack messages. This is fixed in 3.11
3.10
Add require_ack parameter to async subscribe.
I need this for windows so that we can test how to not loose messages
3.9
Remove ConnectionClosed error from async and never raise it. Instead we want to just loop and attempt to reconnect as normal. If your code is expecting ConnectionClosed in ebosia.async, it will no longer be present, don’t use it
3.8
Now when connecting to RabbitMQ the process will loop indefinitely allowing RabbitMQ to come up. This is for our containerized environments where all containers start at the same time and we don’t want containers to fail just because they started first and faster
Also this bumps up our dependency on aioamqp to the lates (0.8.2) to get some fixes around heartbeats
3.7
Be less dramatic about failure to sync.publish. Instead of an exception-like error log we emit a warning. If we fail all the way we’ll emit a proper exception
3.6
3.5 is a bad tag, don’t use it, don’t download it. It has a pdb.set_trace in the setup.py…
3.5
Add async publishing and a bridge to allow async code to correct call ebosia.sync.publish. It’s wild and wacky, but it should work
3.4
Fix bug with nesting event publishes inside event subscriptions when testing
3.3
Automatically serialize UUIDs and datetimes. This means that you can be less careful about what you push through ebosia. No I don’t currently support a custom formatter, sorry, send me a PR
3.2
Allow more control when subscribing like specifying the durability and exclusivity. This can be useful for making exchanges and queues that last longer than the connection to the client
3.1
Allow eventbus fixture’s published() function to not specify the payload. This is nice if your code emits very large or very complex events and you don’t want to have to fully check that payload in every test
3.0
Rename the package to ebosia so that I can publish on PyPI
2.3
Fix synchronous subscription. I had broken it in some previous update
2.2
Allow publishing enums as event topics. This modifies the default JSON serializer a bit so that it attempts to convert anything passed through to a string which is nice for items coming out of a database
2.1
Automatically retry on connection failure when synchronously publishing. Also fix the sync-emitter script. And include it on installation
2.0
Update kombo package to 3.0.34
1.9
Make heartbeat default to 60 seconds but configurable to whatever you want
1.8
Add default heartbeat for async connections of 60 seconds.
1.7
Add reconnect logic for async subscribers. Subscribers now need to supply on_reconnect when calling connect. on_reconnect should be a coroutine that sets up the subscriptions whenever a reconnection is made
1.6
Make the connection stateful in the global state. Whenever a connection is made we’ll keep it in a global location so that clients can get it via ebosia.get(). This means a client doesn’t need to pass the connection around everywhere
2 maintainers
Metadata
2 maintainers
Release files for ebosia 3.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ebosia-3.18.tar.gz | 9.6 kB | Without provenance | Details |
Release files / ebosia-3.18.tar.gz
| Download URL | ebosia-3.18.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92980bcb284fb795417c53f713ec873a9d4d57f6344f195e2e6f6a5c111150c6
|
|
BLAKE2b-256 checksum How to use checksums |
3a92ef62b2f53d63f5817120a8c562046bcd6ace273ac1e4fc78c6b7521b6d53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ebosia 3.18
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
