Skip to main content

A library for getting events throughout the system

Project description


A library for dealing with getting arbitrary events moving throughout the system



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


Loosen up requirements for dev dependencies


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


Don’t use release 3.10, it will never ack messages. This is fixed in 3.11


Add require_ack parameter to async subscribe.

I need this for windows so that we can test how to not loose messages


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


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


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.5 is a bad tag, don’t use it, don’t download it. It has a pdb.set_trace in the…


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


Fix bug with nesting event publishes inside event subscriptions when testing


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


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


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


Rename the package to ebosia so that I can publish on PyPI


Fix synchronous subscription. I had broken it in some previous update


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


Automatically retry on connection failure when synchronously publishing. Also fix the sync-emitter script. And include it on installation


Update kombo package to 3.0.34


Make heartbeat default to 60 seconds but configurable to whatever you want


Add default heartbeat for async connections of 60 seconds.


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


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

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

ebosia-3.18.tar.gz (9.6 kB view hashes)

Uploaded source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page