celery-bittensor
Bittensor's Schedule for Celery
Installation
pip install celery-bittensor
Requires Python 3.10+.
Example
import celery
import celery_bittensor
app = celery.Celery()
@app.on_after_configure.connect
def setup_periodic_tasks(sender: celery.Celery, **kwargs):
# Calls test('hello') every 10 finalized blocks.
sender.add_periodic_task(
celery_bittensor.schedule(run_every=10),
test.s("hello"),
name="add every 10",
)
# Calls test('hello') every 10 finalized blocks relative to block number 0.
sender.add_periodic_task(
celery_bittensor.schedule(run_every=10, relative=True),
test.s("hello"),
name="add every 10 relative to 0",
)
# Calls test('hello') every 10 new blocks on testnet.
sender.add_periodic_task(
celery_bittensor.schedule(run_every=10, finalized=False, network="test"),
test.s("hello"),
name="add every 10 on testnet",
)
@app.task
def test(arg):
print(arg)
License
BSD 3-Clause License, see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for celery-bittensor 0.2.1
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 |
|---|---|---|---|---|
| celery_bittensor-0.2.1.tar.gz | 7.7 kB | With provenance | Details for celery_bittensor-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| celery_bittensor-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for celery_bittensor-0.2.1-py3-none-any.whl |
Total release size: 13.5 kB
Release files / celery_bittensor-0.2.1.tar.gz
| Download URL | celery_bittensor-0.2.1.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c7bd9177fa80ce5da9562aec79c9104929931ef209d825f6ac9fe7209a027f9
|
|
BLAKE2b-256 checksum How to use checksums |
f5bbd0ac18a961c77d2a05f974dcad9b148e7303a48650f52f4a00f9da0a925e
|
| 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 29, 2026.
Transparency logRelease files / celery_bittensor-0.2.1-py3-none-any.whl
| Download URL | celery_bittensor-0.2.1-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
380ef4ffe3723c647f94d4e706e5f29727c9fb1927e42f226f3fecb2826e5c49
|
|
BLAKE2b-256 checksum How to use checksums |
3ba8cebe4bfa00ca315c93c700853ac2f6d3cdaa80b99fa30e8a129e68dbd1a3
|
| 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 29, 2026.
Transparency logSecurity for celery-bittensor 0.2.1
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 celery_bittensor-0.2.1.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 29, 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.
