Python client and module for Lacus
Use this module to interact with a Lacus instance.
Installation
pip install pylacus
Usage
Command line
You can use the pylacus command:
$ pylacus -h
usage: pylacus [-h] --url-instance URL_INSTANCE [--redis_up] {enqueue,status,result} ...
Query a Lacus instance.
positional arguments:
{enqueue,status,result}
Available commands
enqueue Enqueue a url for capture
status Get status of a capture
result Get result of a capture.
options:
-h, --help show this help message and exit
--url-instance URL_INSTANCE
URL of the instance.
--redis_up Check if redis is up.
Library
See API Reference
Example
Enqueue
from pylacus import PyLacus
lacus = PyLacus("http://127.0.0.1:7100")
uuid = lacus.enqueue(url='google.fr')
Status of a capture
status = lacus.get_capture_status(uuid)
Capture result
result = lacus.get_capture(uuid)
Metadata
Release files for pylacus 1.28.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 | |
|---|---|---|---|---|
| pylacus-1.28.0.tar.gz | 6.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pylacus-1.28.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.2 kB
Release files / pylacus-1.28.0.tar.gz
| Download URL | pylacus-1.28.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e536cb1dfdcad04ee4d9e0d5e32c8b81d441815b46d86f19e505496be42f7484
|
|
BLAKE2b-256 checksum How to use checksums |
30a9fa4bb58e7307003c697af3aaef1dba74b56c0361ef79db6a2a2caf86c7bb
|
| 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 Oct 24, 2026.
Transparency logRelease files / pylacus-1.28.0-py3-none-any.whl
| Download URL | pylacus-1.28.0-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f2538c96293ba54a906895c74646330afcb8f81c7c75e57b1caf324c7359343
|
|
BLAKE2b-256 checksum How to use checksums |
a393347e2b32b46413095915c4d00aa99494a8477db63d71140febc398e68ccc
|
| 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 Oct 24, 2026.
Transparency logSecurity for pylacus 1.28.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 pylacus-1.28.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 24, 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.