This release is a pre-release and may not be stable for production use.
Rejected
Rejected is an AMQP consumer daemon and message processing framework. It allows for rapid development of message processing consumers by handling all of the core functionality of communicating with RabbitMQ and management of consumer processes.
Rejected runs as a master process with multiple consumer configurations that are each run in an isolated process. It has the ability to collect statistical data from the consumer processes and report on it.
Features
- Async consumers built on
asyncio - Automatic exception handling including connection management and consumer restarting
- Smart consumer classes that automatically decode and deserialize message bodies based on message headers
- Concurrent message processing with
FunctionalConsumer - Metrics via statsd and/or Prometheus
- Built-in profiling of consumer code
- Avro schema support with file and HTTP schema registries
- YAML and TOML configuration file support
Installation
pip install rejected
For optional features:
pip install rejected[avro] # Avro datum serialization
pip install rejected[html] # HTML message body support
pip install rejected[msgpack] # MessagePack support
pip install rejected[prometheus] # Prometheus metrics exporter
pip install rejected[sentry] # Sentry error reporting
Documentation
Full documentation is available at https://gmr.github.io/rejected.
Example Consumer
import logging
import rejected
LOGGER = logging.getLogger(__name__)
class Test(rejected.Consumer):
async def process(self) -> None:
LOGGER.debug('In Test.process: %s', self.body)
For concurrent message processing, use FunctionalConsumer:
import logging
import rejected
LOGGER = logging.getLogger(__name__)
class Test(rejected.FunctionalConsumer):
async def process(self, ctx: rejected.ProcessingContext) -> None:
LOGGER.debug('Processing: %s', ctx.message.body)
Metadata
Release files for rejected 4.0.0b2
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 | Actions |
|---|---|---|---|---|
| rejected-4.0.0b2.tar.gz | 140.8 kB | With provenance | Details for rejected-4.0.0b2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rejected-4.0.0b2-py3-none-any.whl | Python 3 | none | any | Details for rejected-4.0.0b2-py3-none-any.whl |
Total release size: 194.3 kB
Release files / rejected-4.0.0b2.tar.gz
| Download URL | rejected-4.0.0b2.tar.gz |
|---|---|
| Size | 140.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad38378e864716dcce0a6415334c1afefc04be0265ed45b8268a76e23fb6acda
|
|
BLAKE2b-256 checksum How to use checksums |
bd683574dabca4e9f4a3e22f40fc655b9e0e8cb20fb41054fb442e1e69aab281
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logRelease files / rejected-4.0.0b2-py3-none-any.whl
| Download URL | rejected-4.0.0b2-py3-none-any.whl |
|---|---|
| Size | 53.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee6358c1f544401e6301760c85cee176588c92d65e9f1ae51355d5fe3baeb667
|
|
BLAKE2b-256 checksum How to use checksums |
225e7918f5482053450c530d776037a25438fcd89d8adc9ea60420b0ea8b5d3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logSecurity for rejected 4.0.0b2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for rejected-4.0.0b2.tar.gz
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 Nov 10, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.