celery-types
Type stubs for celery related projects:
install
pip install celery-types
You'll also need to monkey patch the classes from the example below (you can delete anything you don't intend to use) so generic params can be provided:
from celery import Celery, Signature
from celery.app.task import Task
from celery.contrib.abortable import AbortableAsyncResult, AbortableTask
from celery.contrib.django.task import DjangoTask
from celery.local import class_property
from celery.result import AsyncResult
from celery.utils.objects import FallbackContext
classes = [
Celery,
Task,
DjangoTask,
AbortableTask,
AsyncResult,
AbortableAsyncResult,
Signature,
FallbackContext,
class_property,
]
for cls in classes:
setattr( # noqa: B010
cls,
"__class_getitem__",
classmethod(lambda cls, *args, **kwargs: cls),
)
dev
initial setup
# install uv (https://docs.astral.sh/uv/)
curl -LsSf https://astral.sh/uv/install.sh | sh
regular development
uv sync
# run formatting, linting, and typechecking
s/lint
or
uv run ruff check --fix
uv run ruff format
uv run basedpyright typings tests
uv run mypy tests
# build and publish
uv build && uv publish
pre-commit
The project uses pre-commit for code quality checks:
# install pre-commit hooks
uv run prek install
# run all checks manually
uv run prek run --all-files
tooling
- ruff — formatting and linting
- basedpyright — type checking
- mypy — type checking
related
Metadata
Release files for celery-types 0.26.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 | Actions |
|---|---|---|---|---|
| celery_types-0.26.0.tar.gz | 106.2 kB | Without provenance | Details for celery_types-0.26.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| celery_types-0.26.0-py3-none-any.whl | Python 3 | none | any | Details for celery_types-0.26.0-py3-none-any.whl |
Total release size: 317.5 kB
Release files / celery_types-0.26.0.tar.gz
| Download URL | celery_types-0.26.0.tar.gz |
|---|---|
| Size | 106.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa318136fdad83f83f1531deecd9fe664b5dfffff29f3c31e9120a46b8e3908f
|
|
BLAKE2b-256 checksum How to use checksums |
fc38813dd7534e41682684d3a5c2cc4a8710e3acc51b364920b9c4d747c7b18f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.9 {"installer":{"name":"uv","version":"0.9.9"},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / celery_types-0.26.0-py3-none-any.whl
| Download URL | celery_types-0.26.0-py3-none-any.whl |
|---|---|
| Size | 211.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb9da76f461786091970df466ec647d9a27956399852542cb6cab9309970f950
|
|
BLAKE2b-256 checksum How to use checksums |
d9e5c5ec98f7fd7817d077c9a5a5e705d54f74d4ca08ee3f14dee881c93c0511
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.9 {"installer":{"name":"uv","version":"0.9.9"},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for celery-types 0.26.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.