QueueWorker
QueueWorker is asynchronous Task Queue implementation built to
work with asyncio.
Can you spawn distributed workers to run functions inside workers and outside of
event loop.
QueueWorker requires Python 3.8+ and is distributed under MIT license.
How do I get set up?
First, you need to instal QueueWorker:
.. code-block ::
pip install qworker
Then, you can start several workers (even sharing the same port):
.. code-block ::
qw --host --port --worker
where
<hostname>is a hostname of the server<port-number>is a port that server will listen on<num-workers>is a number of worker processes
License
QueueWorker is copyright of Jesus Lara (https://phenobarbital.info) and is under MIT license. I am providing code in this repository under an open source license, remember, this is my personal repository; the license that you receive is from me and not from my employeer.
2 maintainers
Metadata
2 maintainers
Release files for qworker 1.12.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 1.8 MB
Release files / qworker-1.12.4-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | qworker-1.12.4-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 504.8 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
d8853d8fa7832efd69a242b2951a711b6cbbbe59d5dd15e6786b065753a3813d
|
|
BLAKE2b-256 checksum How to use checksums |
6b203e9bfe6dcf497065a5635f67a2d076bfc95f0b6dd36a49c2cfac672c90c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / qworker-1.12.4-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | qworker-1.12.4-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 467.6 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
c5da37d3ac57375e371e921fd004c5a07e347fdebc5d84b18e285922b5db6447
|
|
BLAKE2b-256 checksum How to use checksums |
b0ad2c0d98adcfe6e46e8def59108f6b75785ed0995c57997870bda3b9008213
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / qworker-1.12.4-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | qworker-1.12.4-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 434.0 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
9277f1fde9c191b88de4a75ac672843dc0e52c685915d911b49fe5f38bfefe28
|
|
BLAKE2b-256 checksum How to use checksums |
c90d2baee47fdaefe075e2820760ed6eb7970320b07b473d669b2d3bc3a74f66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / qworker-1.12.4-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | qworker-1.12.4-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 438.9 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
8a2bd81ed3b2988f594da5a4b0dac23695baccb43778a4a2c3aee31f6b3147ec
|
|
BLAKE2b-256 checksum How to use checksums |
d71f5027097b1c77004a447fbb591c9265d869223eef1227230a464df7cf53e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for qworker 1.12.4
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.
