This module is used for interprocess communication (IPC) for processes in difference namespaces.I designed and wrote this module because existing IPC libraries are not suitable for inter-namespaces communication.Currently, I have implemented a JSON-RPC interface.
1 maintainer
Metadata
1 maintainer
Release files for procslink 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| procslink-0.1.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Release files / procslink-0.1.2-py2.py3-none-any.whl
| Download URL | procslink-0.1.2-py2.py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
54aa152cb4a4d0cd3010c14663a8d1f110e6359447c2a151ca5087d9873b7a30
|
|
BLAKE2b-256 checksum How to use checksums |
79746220b3a96408e35f5b0d45e066148a5a4006a8d6a28e88a7e41ab2c7671e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for procslink 0.1.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.
