A simple and synchronous message queue for commands and events for Django.
PyPI • GitHub • Full documentation
Creator & Maintainer: Beyonder Deutschland
Features
- Split up your business logic in commands and events
- Commands are imperatives telling your system what to do, events reflect that something has happened
- Register light-weight functions via a decorator to listen to your commands and events
- Message handlers receive the context of the message (command or event), providing an explicit API
- No magic, no side effects since the queue works synchronously
import dataclasses
from queuebie.runner import handle_message
from queuebie.messages import Command, Event
from queuebie import message_registry
# Example command
@dataclasses.dataclass(kw_only=True)
class BuyProduct(Command):
product_id: int
customer_id: int
price: float
currency: str
# Example event
@dataclasses.dataclass(kw_only=True)
class ProductBought(Event):
product_id: int
customer_id: int
# Example handler
@message_registry.register_command(BuyProduct)
def handle_buy_product(context: BuyProduct) -> Event:
# Here lives your business logic
return ProductBought(
product_id=context.product_id,
customer_id=context.customer_id,
)
# Start queue and process messages
handle_message(
BuyProduct(
product_id=product.id,
customer_id=customer.id,
price=12.99,
currency="EUR",
)
)
Installation
-
Install the package via pip:
pip install django_queuebieor via uv:
uv add django_queuebie -
Add module to
INSTALLED_APPSwithin the main djangosettings.py:
INSTALLED_APPS = (
# ...
"queuebie",
)
Releasing a new version
Releases are fully automated. Push a version tag and the pipeline will build, sign with Sigstore, publish to PyPI via Trusted Publishing, and create a GitHub Release — no API tokens needed.
git tag v<version> # e.g. git tag v1.2.3
git push origin v<version>
Tags must start with v. Tags without the prefix won't trigger the pipeline.
First-time setup
Before the pipeline can run for the first time, an admin must:
-
Create GitHub Environment
pypi- Go to Settings → Environments → New environment, name it exactly
pypi - Under Deployment branches and tags, add a tag rule with pattern
v* - Optionally add required reviewers for a manual approval gate
- Go to Settings → Environments → New environment, name it exactly
-
Configure PyPI Trusted Publisher
- Go to PyPI → Project settings → Publishing → Add a new publisher
- Fill in: Owner
ambient-innovation, Repositorydjango-queuebie, Workflowrelease.yml, Environmentpypi
Publish to ReadTheDocs.io
- Fetch the latest changes in GitHub mirror and push them
- Trigger new build at ReadTheDocs.io (follow instructions in admin panel at RTD) if the GitHub webhook is not yet set up.
Maintenance
Please note that this package supports the ambient-package-update.
So you don't have to worry about the maintenance of this package. This updater is rendering all important
configuration and setup files. It works similar to well-known updaters like pyupgrade or django-upgrade.
To run an update, refer to the documentation page of the "ambient-package-update".
Release files for django-queuebie 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_queuebie-0.6.0.tar.gz | 105.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_queuebie-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 118.8 kB
Release files / django_queuebie-0.6.0.tar.gz
| Download URL | django_queuebie-0.6.0.tar.gz |
|---|---|
| Size | 105.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1a9def900b4736ec0ea905995db6fd1799d9f2a619f7801d9e3fa24b9e8f18b
|
|
BLAKE2b-256 checksum How to use checksums |
337279045effbc4150f9b90dba23c0f33af29a31ff3e74160f670466293842f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / django_queuebie-0.6.0-py3-none-any.whl
| Download URL | django_queuebie-0.6.0-py3-none-any.whl |
|---|---|
| Size | 13.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f7c554973702bd3094e2a6907818608d57df1324e0f11d8ae3867ad2248103f
|
|
BLAKE2b-256 checksum How to use checksums |
86e6e506688c4bb3b5bf314521b085bc5c7b9f7cf65fc8a2b19b6f27cf808fc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency log