celery-pubsub 1.0.2
Publish and Subscribe with Celery
Supported dependencies
| Python | Celery 3 | Celery 4 | Celery 5 |
|---|---|---|---|
| 2.7 | |||
| 3.5 | |||
| 3.6 | |||
| 3.7 | |||
| 3.8 | |||
| 3.9 | |||
| 3.10 | |||
| pypy 2.7 | |||
| pypy 3.6 |
Basic usage
import celery
import celery_pubsub
@celery.task
def my_task_1(*args, **kwargs):
return "task 1 done"
@celery.task
def my_task_2(*args, **kwargs):
return "task 2 done"
# First, let's subscribe
celery_pubsub.subscribe('some.topic', my_task_1)
celery_pubsub.subscribe('some.topic', my_task_2)
# Now, let's publish something
res = celery_pubsub.publish('some.topic', data='something', value=42)
# We can get the results if we want to (and if the tasks returned something)
# But in pub/sub, usually, there's no result.
print(res.get())
# This will get nowhere, as no task subscribed to this topic
res = celery_pubsub.publish('nowhere', data='something else', value=23)
Advanced usage
Wildcards can be used in topic names:
-
*matches any one groupsome.*.testwill matchsome.awesome.test,some.random.testbut notsome.pretty.cool.test,elsewhereorhere.some.up.testsome.*will matchsome.testandsome.thingbut it won't matchsomeorsome.testy.test
-
#matches any number of groupssome.#.testwill matchsome.awesome.test,some.random.test,some.pretty.cool.testbut notelsewhereorhere.some.up.testsome.#will match anything that starts withsome., such assome.very.specific.topic.indeed#will match anything
# Let's subscribe
celery_pubsub.subscribe('some.*', my_task_1)
celery_pubsub.subscribe('some.*.test', my_task_2)
celery_pubsub.subscribe('some.#', my_task_3)
celery_pubsub.subscribe('#', my_task_4)
celery_pubsub.subscribe('some.beep', my_task_5)
# it's okay to have more than one task on the same topic
celery_pubsub.subscribe('some.beep', my_task_6)
# Let's publish
celery_pubsub.publish('nowhere', 4) # task 4 only
celery_pubsub.publish('some', 8) # task 4 only
celery_pubsub.publish('some.thing', 15) # tasks 1, 3 and 4
celery_pubsub.publish('some.true.test', 16) # tasks 2, 3 and 4
celery_pubsub.publish('some.beep', 23) # tasks 1, 3, 4, 5 and 6
celery_pubsub.publish('some.very.good.test', 42) # tasks 3 and 4
# And if you want to publish synchronously:
celery_pubsub.publish_now('some.very.good.test', 42) # tasks 3 and 4
# You can unsubscribe too
celery_pubsub.unsubscribe('#', my_task_4)
# Now, task 4 will not be called anymore
celery_pubsub.publish('some.very.good.test', 42) # task 3 only
Changelog
- 1.0.2
- Add stubs file for type hinting.
- 1.0.1
- Changed
README.rsttoREADME.md. - Added better badges to show the supported status for each Celery & Python version.
- Changed
- 1.0.0
- Flexible requirements (no more pinned). Better to support a wide range of environments.
- Changed test framework from nose to pytest.
- Flake8
- Support for Python 3.9 and 3.10.
- 0.2.1
- Performance: Internally uses a
setto store the subscribed tasks. - Updated Codeclimate as the
old reporter <https://github.com/codeclimate/python-test-reporter>_ is deprecated. - Pinned requirements' dependency versions.
- celery 4.3.0 -> 4.4.0
- kombu 4.6.4 -> 4.6.7
- billiard 3.6.1.0 -> 3.6.2.0
- codeclimate-test-reporter 0.2.3 -> removed!
- Performance: Internally uses a
- 0.2.0
- Removed Python 3.4 support. Reason: no longer supported by Kombu 4.6+.
- Officially supported by Python 3.8.
- Pinned requirements' dependency versions.
- celery 4.2.1 -> 4.3.0
- kombu 4.2.1 -> 4.6.4
- billiard 3.5.0.4 -> 3.6.1.0
- vine 1.1.4 -> 1.3.0
- 0.1.9
- Added Python 3.4, 3.5, 3.7, and multiple branches of pypy
- Pinned requirements' dependency versions.
- celery 4.1.0 -> 4.2.1
- kombu 4.1.0 -> 4.2.1
- billiard 3.5.0 -> 3.5.0.4
- nose pinned to 1.3.7
- coverage pinned to 4.3.4 (was already 4.3.4 but fuzzy)
- codeclimate-test-reported pinned to 0.2.3
- Extra badge to show the number of downloads (thanks to PePy)
- 0.1.8
- Fixup for broken
pip install celery_pubsub==0.1.7
- Fixup for broken
- 0.1.7
- PyPI long description fixed
- Removed README.md and fixed README.rst
- Added command
python setup.py testto run unit tests with coverage - pypy support
- 0.1.5
- Python 3 support
- 0.1.1
- Added README
- Refined setup
- No need to access celery_pubsub.pubsub anymore. Direct access in celery_pubsub.
- Tests moved out of package
- Added Travis for CI
- 0.1
- Initial version
Metadata
Release files for celery-pubsub 1.0.2
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-pubsub-1.0.2.tar.gz | 7.1 kB | Without provenance | Details for celery-pubsub-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| celery_pubsub-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for celery_pubsub-1.0.2-py3-none-any.whl |
Total release size: 12.9 kB
Release files / celery-pubsub-1.0.2.tar.gz
| Download URL | celery-pubsub-1.0.2.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
95ef48bf6bdd0800ce2c8323019dbc2295ec834cd4aad4f15f6bf220c317ef97
|
|
BLAKE2b-256 checksum How to use checksums |
4df34ec56031ec657744682fa4b3a036507ac67b295829b1e05351062a540b74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Release files / celery_pubsub-1.0.2-py3-none-any.whl
| Download URL | celery_pubsub-1.0.2-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
591092db36075f1fe7cf0e7b666edd3ae4a1aae1ef7b5b3e1569a0c81bd9f382
|
|
BLAKE2b-256 checksum How to use checksums |
681277edeefc4ec284ab9189e572793fd7a4d72cebaf7883253841131206b6b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for celery-pubsub 1.0.2
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.