mersal 0.0.2__tar.gz

mersal-0.0.2/.gitignore

@@ -0,0 +1,203 @@
+
+# Created by https://www.toptal.com/developers/gitignore/api/python,emacs
+# Edit at https://www.toptal.com/developers/gitignore?templates=python,emacs
+
+*.DS_Store
+### Emacs ###
+# -*- mode: gitignore; -*-
+*~
+\#*\#
+/.emacs.desktop
+/.emacs.desktop.lock
+*.elc
+auto-save-list
+tramp
+.\#*
+
+# Org-mode
+.org-id-locations
+*_archive
+
+# flymake-mode
+*_flymake.*
+
+# eshell files
+/eshell/history
+/eshell/lastdir
+
+# elpa packages
+/elpa/
+
+# reftex files
+*.rel
+
+# AUCTeX auto folder
+/auto/
+
+# cask packages
+.cask/
+dist/
+
+# Flycheck
+flycheck_*.el
+
+# server auth directory
+/server/
+
+# projectiles files
+.projectile
+
+# directory configuration
+.dir-locals.el
+
+# network security
+/network-security.data
+
+
+### Python ###
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+docs-build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# End of https://www.toptal.com/developers/gitignore/api/python,emacs
+#
+.projectile-cache.eld
+DOCUMENTATION_STRATEGY.md
+SPACE_MISSION_CONTROL_THEME.md
+LOGO_USAGE_GUIDE.md
+mersal-*.svg

mersal-0.0.2/.pre-commit-config.yaml

@@ -0,0 +1,54 @@
+---
+ci:
+  autoupdate_schedule: monthly
+
+default_language_version:
+  python: "3.13"
+repos:
+  - repo: https://github.com/compilerla/conventional-pre-commit
+    rev: v4.4.0
+    hooks:
+      - id: conventional-pre-commit
+        stages: [commit-msg]
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: check-ast
+      - id: check-case-conflict
+      - id: check-toml
+      - id: debug-statements
+        exclude: ^(mersal/retry/default_retry_step\.py)$
+      - id: end-of-file-fixer
+      - id: mixed-line-ending
+      - id: trailing-whitespace
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.0
+    hooks:
+      - id: ruff-check
+        args: [--fix, --exit-non-zero-on-fix]
+      - id: ruff-format
+  - repo: https://github.com/crate-ci/typos
+    rev: "v1"
+    hooks:
+      - id: typos
+  - repo: https://github.com/python-formate/flake8-dunder-all
+    rev: v0.6.0
+    hooks:
+      - id: ensure-dunder-all
+        exclude: "tools"
+        args: ["--use-tuple"]
+  - repo: https://github.com/sphinx-contrib/sphinx-lint
+    rev: "v1.0.2"
+    hooks:
+      - id: sphinx-lint
+  - repo: https://github.com/abravalheri/validate-pyproject
+    rev: v0.25
+    hooks:
+      - id: validate-pyproject
+        # Optional extra validations from SchemaStore:
+        additional_dependencies: ["validate-pyproject-schema-store[all]"]
+  - repo: https://github.com/econchick/interrogate
+    rev: 1.7.0
+    hooks:
+      - id: interrogate
+        args: [tests]

mersal-0.0.2/.python-version

@@ -0,0 +1 @@
+3.13

mersal-0.0.2/CNAME

@@ -0,0 +1 @@
+docs.mersal.dev

mersal-0.0.2/CONTRIBUTING.rst

@@ -0,0 +1,82 @@
+Contributing
+=============
+
+Development setup
+------------------
+
+Mersal uses `uv <https://docs.astral.sh/uv/>`_ for dependency management and
+`mise <https://mise.jdx.dev/>`_ to run project tasks.
+
+.. code-block:: shell
+
+   mise run install    # create the venv, install deps, install pre-commit hooks
+   mise run test        # run the test suite
+   mise run lint        # format + run pre-commit
+   mise run type-check   # ty + basedpyright + mypy
+   mise run docs:serve   # live-reloading docs server
+
+Run ``mise tasks`` to see everything available.
+
+Versioning
+----------
+
+Mersal follows `Semantic Versioning <https://semver.org/>`_.
+
+The version number is **never** hand-edited in ``pyproject.toml``. It is
+derived entirely from git tags via `hatch-vcs
+<https://github.com/ofek/hatch-vcs>`_:
+
+- On a commit that is exactly a tag (e.g. ``v1.2.3``), the package version is
+  ``1.2.3``.
+- On any other commit, the version is a development version derived from the
+  most recent tag, e.g. ``1.2.4.dev3`` for the 3rd commit after ``v1.2.3``.
+
+This means making a release is just a matter of pushing a tag -- there is no
+version-bump commit or changelog-file merge conflict to manage.
+
+Making a release
+-----------------
+
+1. Make sure ``main`` is green (CI passing) and contains everything you want
+   to ship.
+2. Decide the next version per SemVer:
+
+   - **patch** (``1.2.3`` -> ``1.2.4``): bug fixes only, no API changes.
+   - **minor** (``1.2.3`` -> ``1.3.0``): new, backwards-compatible functionality.
+   - **major** (``1.2.3`` -> ``2.0.0``): breaking changes.
+
+3. Tag the release and push the tag:
+
+   .. code-block:: shell
+
+      git tag v1.2.4
+      git push origin v1.2.4
+
+4. Go to `GitHub Releases
+   <https://github.com/mersal-org/mersal/releases/new>`_, pick the tag you
+   just pushed, click **Generate release notes** (GitHub builds these from
+   merged PR titles -- keep PR titles/commits following `Conventional
+   Commits <https://www.conventionalcommits.org/>`_, which is already
+   enforced by pre-commit), review, and click **Publish release**.
+
+5. Publishing the release triggers `.github/workflows/publish.yml
+   <.github/workflows/publish.yml>`_, which builds the package with the
+   version baked in from the tag and uploads it to PyPI using `Trusted
+   Publishing <https://docs.pypi.org/trusted-publishers/>`_ -- no API tokens
+   involved.
+
+Continuous pre-releases on Test PyPI
+-------------------------------------
+
+Every push to ``main`` (i.e. every merged PR) automatically builds the
+package and uploads it to `Test PyPI
+<https://test.pypi.org/project/mersal/>`_ under its dev version
+(e.g. ``1.2.4.dev3``). This lets you or early adopters install and sanity
+check the very latest ``main`` before it's ever cut into a real release:
+
+.. code-block:: shell
+
+   pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple mersal
+
+This mirrors the workflow used by projects like `structlog
+<https://github.com/hynek/structlog/blob/main/.github/workflows/pypi-package.yml>`_.

mersal-0.0.2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023-present Abdulhaq Emhemmed
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

mersal-0.0.2/PKG-INFO

@@ -0,0 +1,155 @@
+Metadata-Version: 2.4
+Name: mersal
+Version: 0.0.2
+Summary: A service bus library.
+Project-URL: Homepage, https://github.com/mersal-org/mersal
+Project-URL: Documentation, https://docs.mersal.dev
+Project-URL: Repository, https://github.com/mersal-org/mersal
+Project-URL: Changelog, https://github.com/mersal-org/mersal/releases
+Project-URL: Issue Tracker, https://github.com/mersal-org/mersal/issues
+Author-email: Abdulhaq Emhemmed <abdulhaq.emhemmed@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: async,asyncio,message bus,messaging,sagas,service bus
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: Intended Audience :: System Administrators
+Classifier: Natural Language :: English
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Internet
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: anyio>=4.8.0
+Description-Content-Type: text/x-rst
+
+Mersal
+=======
+
+.. list-table::
+   :header-rows: 1
+
+   * - Project
+     - Status
+   * - CI/CD
+     - .. image:: https://github.com/mersal-org/mersal/actions/workflows/publish.yml/badge.svg
+          :target: https://github.com/mersal-org/mersal/actions/workflows/publish.yml
+          :alt: Latest Release
+       .. image:: https://github.com/mersal-org/mersal/actions/workflows/ci.yml/badge.svg
+          :target: https://github.com/mersal-org/mersal/actions/workflows/ci.yml
+          :alt: CI
+       .. image:: https://github.com/mersal-org/mersal/actions/workflows/docs.yml/badge.svg?branch=main
+          :target: https://github.com/mersal-org/mersal/actions/workflows/docs.yml
+          :alt: Documentation Building
+   * - Quality
+     - .. image:: https://codecov.io/github/mersal-org/mersal/graph/badge.svg?token=3219SZABYN
+          :target: https://codecov.io/github/mersal-org/mersal
+   * - Package
+     - .. image:: https://img.shields.io/pypi/v/mersal?labelColor=202235&color=1e4b94&logo=python&logoColor=white
+          :target: https://badge.fury.io/py/mersal
+          :alt: PyPI - Version
+       .. image:: https://img.shields.io/pypi/pyversions/mersal?labelColor=202235&color=1e4b94&logo=python&logoColor=white
+          :alt: PyPI - Support Python Versions
+       .. image:: https://img.shields.io/pypi/dm/mersal?logo=python&label=package%20downloads&labelColor=202235&color=1e4b94&logoColor=white
+          :alt: Mersal PyPI - Downloads
+   * - Meta
+     - .. image:: https://img.shields.io/badge/license-MIT-202235.svg?logo=python&labelColor=202235&color=1e4b94&logoColor=white
+          :target: https://spdx.org/licenses/
+          :alt: License - MIT
+       .. image:: https://img.shields.io/badge/types-ty-202235.svg?logo=python&labelColor=202235&color=1e4b94&logoColor=white
+          :target: https://github.com/astral-sh/ty
+          :alt: types - ty
+       .. image:: https://img.shields.io/badge/types-Basedpyright-202235.svg?logo=python&labelColor=202235&color=1e4b94&logoColor=white
+          :target: https://github.com/DetachHead/basedpyright
+          :alt: types - Basedpyright
+       .. image:: https://img.shields.io/badge/types-Mypy-202235.svg?logo=python&labelColor=202235&color=1e4b94&logoColor=white
+          :target: https://github.com/python/mypy
+          :alt: types - Mypy
+       .. image:: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/charliermarsh/ruff/main/assets/badge/v2.json&labelColor=202235&color=1e4b94
+          :target: https://github.com/astral-sh/ruff
+          :alt: linting - Ruff
+
+**Mersal** is a service bus library for Python. It helps you build message driven systems (a.k.a event driven architecture).
+
+There will be more here eventually but here is an LLM summary of core features in Mersal:
+
+* **Transport agnostic**: AWS SNS/SQS, GCP Pub/Sub, RabbitMQ, Azure Servicebus, it's your choice!
+* **Pub/sub** - subscribe to events across independently running apps, with
+  autosubscribe support so wiring stays out of your way.
+* **Sagas** - coordinate a business process that spans multiple messages
+  over time, with pluggable storage for the saga's state.
+* **The outbox pattern** - persist outgoing messages in the same transaction
+  as your business data, so a handler's side effects and its database write
+  succeed or fail together.
+* **Idempotent handling** - process the same message more than once without
+  corrupting state.
+* **Retries and error handling** - configurable retry strategies with
+  dead-lettering to an error queue once a message keeps failing, so nothing
+  is silently dropped.
+* **A transport bridge** - route messages to specific destinations through a
+  different transport than the rest of the system, useful for migrations,
+  cost/efficiency tradeoffs, or testing.
+* **Pluggable persistence, and serialization**
+* **Unit of work and a request/response-style pipeline** - hook into message
+  handling to add your own cross-cutting behavior, the same way middleware
+  works in a web framework.
+
+Head to the `quick start <https://docs.mersal.dev/latest/quickstart.html>`_ to
+build a small message-driven system in a few minutes, or the full
+`documentation <https://docs.mersal.dev>`_ for everything else.
+
+Acknowledgments ♥
+-------------------
+
+This is a personal acknowledgment from myself (@abdulhaq-e), the main author of Mersal.
+
+First, to the book `Architecture Patterns with Python
+<https://www.cosmicpython.com/>`_ ("Cosmic Python") and its two authors,
+Harry Percival (@hjwp) and Bob Gregory (@bobthemighty). Its
+impact on my career is substantial and cannot be compared to any other material
+I came by. In addition, the book is why we have Mersal.
+
+I was following the book before its official release via its git repository. I
+completed every example, studied all patterns, read all the side material and
+years later, I still go back to it. It is like watching and rewatching a
+favourite TV show! I really recommend anyone who is building systems using
+Python (or any other language actually) to study from this book, especially if
+someone wants to adopt Domain Driven Design (DDD).
+
+In Part 2 of the book, the authors introduce the concept of Event Driven
+Architecture and the idea of a "message bus". Once I started building a system
+and applying my learnings, the system message bus was more or less the message
+bus from the book. From one system to the next, the bus was extracted into a
+reusable package and for years it was "pyservicebus". This now brings me to the
+second acknowledgment. Before that, thank you, Harry and Bob, for writing the
+book, and for putting so much effort into it and for writing/releasing it as an
+open book.  ♥
+
+The current state of Mersal is significantly different than how `pyservicebus`
+looked like. I still have the commits stored somewhere with all the cursing and
+trials.  Building a service bus that abstracts transport mechanism isn't an easy
+job. So why not build on the shoulder of giants. While learning more about the
+concept of a message bus, I did come by NServiceBus and they have great learning
+materials regarding the topic and message driven architecture in general.
+NServicebus is OSS but their product is what you can consider as a gigantic
+framework with all batteries included. When looking for inspiration for Mersal,
+I wanted something lighter and that's when I found `Rebus
+<https://github.com/rebus-org>`_, it's a .NET service bus designed to provide a
+"lean" offering. While Mersal might have drifted since, I'd still agree to
+call it the "Python replica of Rebus". Huge thanks to Mogens Heller Grabe
+(@mookid8000), Rebus's core developer, for building and maintaining it so
+well for so long that it was worth learning from and borrowing this much
+from. ♥
+
+Finally, a shout out to `Litestar <https://github.com/litestar-org>`_. A
+number of things in Mersal, from small utilities to bigger design decisions,
+were copied or heavily inspired by code in the Litestar organization's
+repositories. Thanks to everyone there for building something worth learning
+from and borrowing from as well.

mersal-0.0.2/README.rst

@@ -0,0 +1,123 @@
+Mersal
+=======
+
+.. list-table::
+   :header-rows: 1
+
+   * - Project
+     - Status
+   * - CI/CD
+     - .. image:: https://github.com/mersal-org/mersal/actions/workflows/publish.yml/badge.svg
+          :target: https://github.com/mersal-org/mersal/actions/workflows/publish.yml
+          :alt: Latest Release
+       .. image:: https://github.com/mersal-org/mersal/actions/workflows/ci.yml/badge.svg
+          :target: https://github.com/mersal-org/mersal/actions/workflows/ci.yml
+          :alt: CI
+       .. image:: https://github.com/mersal-org/mersal/actions/workflows/docs.yml/badge.svg?branch=main
+          :target: https://github.com/mersal-org/mersal/actions/workflows/docs.yml
+          :alt: Documentation Building
+   * - Quality
+     - .. image:: https://codecov.io/github/mersal-org/mersal/graph/badge.svg?token=3219SZABYN
+          :target: https://codecov.io/github/mersal-org/mersal
+   * - Package
+     - .. image:: https://img.shields.io/pypi/v/mersal?labelColor=202235&color=1e4b94&logo=python&logoColor=white
+          :target: https://badge.fury.io/py/mersal
+          :alt: PyPI - Version
+       .. image:: https://img.shields.io/pypi/pyversions/mersal?labelColor=202235&color=1e4b94&logo=python&logoColor=white
+          :alt: PyPI - Support Python Versions
+       .. image:: https://img.shields.io/pypi/dm/mersal?logo=python&label=package%20downloads&labelColor=202235&color=1e4b94&logoColor=white
+          :alt: Mersal PyPI - Downloads
+   * - Meta
+     - .. image:: https://img.shields.io/badge/license-MIT-202235.svg?logo=python&labelColor=202235&color=1e4b94&logoColor=white
+          :target: https://spdx.org/licenses/
+          :alt: License - MIT
+       .. image:: https://img.shields.io/badge/types-ty-202235.svg?logo=python&labelColor=202235&color=1e4b94&logoColor=white
+          :target: https://github.com/astral-sh/ty
+          :alt: types - ty
+       .. image:: https://img.shields.io/badge/types-Basedpyright-202235.svg?logo=python&labelColor=202235&color=1e4b94&logoColor=white
+          :target: https://github.com/DetachHead/basedpyright
+          :alt: types - Basedpyright
+       .. image:: https://img.shields.io/badge/types-Mypy-202235.svg?logo=python&labelColor=202235&color=1e4b94&logoColor=white
+          :target: https://github.com/python/mypy
+          :alt: types - Mypy
+       .. image:: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/charliermarsh/ruff/main/assets/badge/v2.json&labelColor=202235&color=1e4b94
+          :target: https://github.com/astral-sh/ruff
+          :alt: linting - Ruff
+
+**Mersal** is a service bus library for Python. It helps you build message driven systems (a.k.a event driven architecture).
+
+There will be more here eventually but here is an LLM summary of core features in Mersal:
+
+* **Transport agnostic**: AWS SNS/SQS, GCP Pub/Sub, RabbitMQ, Azure Servicebus, it's your choice!
+* **Pub/sub** - subscribe to events across independently running apps, with
+  autosubscribe support so wiring stays out of your way.
+* **Sagas** - coordinate a business process that spans multiple messages
+  over time, with pluggable storage for the saga's state.
+* **The outbox pattern** - persist outgoing messages in the same transaction
+  as your business data, so a handler's side effects and its database write
+  succeed or fail together.
+* **Idempotent handling** - process the same message more than once without
+  corrupting state.
+* **Retries and error handling** - configurable retry strategies with
+  dead-lettering to an error queue once a message keeps failing, so nothing
+  is silently dropped.
+* **A transport bridge** - route messages to specific destinations through a
+  different transport than the rest of the system, useful for migrations,
+  cost/efficiency tradeoffs, or testing.
+* **Pluggable persistence, and serialization**
+* **Unit of work and a request/response-style pipeline** - hook into message
+  handling to add your own cross-cutting behavior, the same way middleware
+  works in a web framework.
+
+Head to the `quick start <https://docs.mersal.dev/latest/quickstart.html>`_ to
+build a small message-driven system in a few minutes, or the full
+`documentation <https://docs.mersal.dev>`_ for everything else.
+
+Acknowledgments ♥
+-------------------
+
+This is a personal acknowledgment from myself (@abdulhaq-e), the main author of Mersal.
+
+First, to the book `Architecture Patterns with Python
+<https://www.cosmicpython.com/>`_ ("Cosmic Python") and its two authors,
+Harry Percival (@hjwp) and Bob Gregory (@bobthemighty). Its
+impact on my career is substantial and cannot be compared to any other material
+I came by. In addition, the book is why we have Mersal.
+
+I was following the book before its official release via its git repository. I
+completed every example, studied all patterns, read all the side material and
+years later, I still go back to it. It is like watching and rewatching a
+favourite TV show! I really recommend anyone who is building systems using
+Python (or any other language actually) to study from this book, especially if
+someone wants to adopt Domain Driven Design (DDD).
+
+In Part 2 of the book, the authors introduce the concept of Event Driven
+Architecture and the idea of a "message bus". Once I started building a system
+and applying my learnings, the system message bus was more or less the message
+bus from the book. From one system to the next, the bus was extracted into a
+reusable package and for years it was "pyservicebus". This now brings me to the
+second acknowledgment. Before that, thank you, Harry and Bob, for writing the
+book, and for putting so much effort into it and for writing/releasing it as an
+open book.  ♥
+
+The current state of Mersal is significantly different than how `pyservicebus`
+looked like. I still have the commits stored somewhere with all the cursing and
+trials.  Building a service bus that abstracts transport mechanism isn't an easy
+job. So why not build on the shoulder of giants. While learning more about the
+concept of a message bus, I did come by NServiceBus and they have great learning
+materials regarding the topic and message driven architecture in general.
+NServicebus is OSS but their product is what you can consider as a gigantic
+framework with all batteries included. When looking for inspiration for Mersal,
+I wanted something lighter and that's when I found `Rebus
+<https://github.com/rebus-org>`_, it's a .NET service bus designed to provide a
+"lean" offering. While Mersal might have drifted since, I'd still agree to
+call it the "Python replica of Rebus". Huge thanks to Mogens Heller Grabe
+(@mookid8000), Rebus's core developer, for building and maintaining it so
+well for so long that it was worth learning from and borrowing this much
+from. ♥
+
+Finally, a shout out to `Litestar <https://github.com/litestar-org>`_. A
+number of things in Mersal, from small utilities to bigger design decisions,
+were copied or heavily inspired by code in the Litestar organization's
+repositories. Thanks to everyone there for building something worth learning
+from and borrowing from as well.

mersal-0.0.2/codecov.yml

@@ -0,0 +1,11 @@
+coverage:
+  status:
+    project:
+      default:
+        target: auto
+        threshold: 0.1%
+    patch:
+      default:
+        target: auto
+comment:
+  require_changes: true

mersal-0.0.2/mersal/__init__.py

@@ -0,0 +1,13 @@
+from importlib.metadata import version
+
+from mersal.logging import Logger, LoggingConfig
+
+__all__ = ["Logger", "LoggingConfig"]
+
+
+def __getattr__(name: str) -> str:
+    if name != "__version__":
+        msg = f"module {__name__!r} has no attribute {name!r}"
+        raise AttributeError(msg)
+
+    return version("mersal")