lowmq-client
An asyncio client for the LowMQ message queue, for Python applications that need to put messages into a LowMQ queue and take them out.
Install
pip install lowmq-client
Example
import asyncio
from lowmq_client import LowMqClient
async def main() -> None:
async with LowMqClient("your-auth-key", "https://lowmq.example.com") as client:
await client.add_packet("payments", {"amount": 100})
message = await client.get_packet("payments", delete=True)
print(message)
asyncio.run(main())
Features
add_packet,get_packetanddelete_packetfor the LowMQ/msgendpoint. Queue names and message ids are URL encoded.async withopens and closes anaiohttp.ClientSession, with a 30 second total timeout by default. Passtimeout=to change it.- Pass your own
session=to reuse an existingaiohttp.ClientSession. The client does not close it. - A non-2xx response from
add_packetorget_packetraisesApiErrorwithstatus,reasonandbody. - A response body that is not JSON is returned as
{"raw": "<text>"}. - The server URL is validated when the client is created. Only
httpandhttpsURLs are accepted; anything else raisesInvalidUrlError. - Type hints and a
py.typedmarker. CI runs mypy in strict mode.
The full API is in docs/api.md.
Limitations and compatibility
- Python 3.10 to 3.14. CI runs the tests on each of these versions, and once more on Python 3.10
with the oldest allowed
aiohttp(3.10.11) andpydantic(2.10). - LowMQ server: no server version is pinned. The client uses the
/msgHTTP endpoint and sendsAuthorization: token <key>. The tests run against an in-process fake server, not a real LowMQ. delete_packetreturnsFalseon a non-2xx response instead of raising.- No retries or batching.
Development
uv sync
uv run coverage run -m unittest -v
uv run coverage report
uv run ruff check .
uv run ruff format --check .
uv run mypy
The tests need no running services. Coverage must stay at 100 percent. uv run pre-commit install
runs ruff and mypy as git hooks, using the versions from uv.lock.
Releases: bump version in pyproject.toml, then push a tag v<version>. CI publishes the
package to PyPI after lint and tests pass.
License
MIT, see LICENSE.
Metadata
Release files for lowmq-client 1.1.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 | Provenance | |
|---|---|---|---|---|
| lowmq_client-1.1.0.tar.gz | 8.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lowmq_client-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.1 kB
Release files / lowmq_client-1.1.0.tar.gz
| Download URL | lowmq_client-1.1.0.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fb3677b89ab26cbf19fd72969b352680a7477e3cf1033502dd06d879ea05b42
|
|
BLAKE2b-256 checksum How to use checksums |
2bd9dadd8da21df78c0fdff06819f0d8f13cad525544b44b3b733a723626939b
|
| 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 Oct 12, 2026.
Transparency logRelease files / lowmq_client-1.1.0-py3-none-any.whl
| Download URL | lowmq_client-1.1.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82183b142a064cbd03f32990798bf4a3e38b8ab11e23d805fe24931822c18df6
|
|
BLAKE2b-256 checksum How to use checksums |
c5c6619ef877a6720f20e19f614df7acd4126590aa53638f0e4456324e5e2eca
|
| 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 Oct 12, 2026.
Transparency logSecurity for lowmq-client 1.1.0
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for lowmq_client-1.1.0.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 Oct 12, 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.