Python Synchronisation Queue
This is a multiprocessing data structure that coordinates a set of child processes in two senses.
- Data - Any connected process can add data to the queue
for all others to read. - Time - Processes can wait on the queue for new data to
be added by any other.
Every process that connects to the same queue is both a reader and writer i.e. it is both a producer and a consumer. But a piece of data is not removed from the queue until every connected process has had a chance to read it. Hence, one process can signal all of the others to respond to the same information.
PyPI package at pypi.org/project/pysyncq
Online documentation at pysyncq.readthedocs.io
GitHub project at github.com/jsdpag/pysyncq
- See docs/_build/html/index.html for basic API documentation.
- See pysyncq/tests/demo.py for a simple demonstration of
basic timing signals and message passing between processes. - See pysyncq/tests/benchmark.py for a simple benchmarking of the message transfer time from a sender to a reader.
Developed by:
0.0.1 - Support for spawn as well as fork child process starting methods. 0.0.0 - Initial release. Functional on Linux.
Metadata
Release files for pysyncq 0.0.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 | |
|---|---|---|---|---|
| pysyncq-0.0.1.tar.gz | 26.8 kB | Without provenance | Details |
Release files / pysyncq-0.0.1.tar.gz
| Download URL | pysyncq-0.0.1.tar.gz |
|---|---|
| Size | 26.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
470c1657106dd546c7a95f1e88d1f67d16b5abd977417c79f0d084530fec1c8a
|
|
BLAKE2b-256 checksum How to use checksums |
28086b967cf7cb561e974b864ae6d10e245a6ffa1d85e9646e0a6fe32bc01830
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for pysyncq 0.0.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.
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.