# RxTender
RxTender is framework to implement code generators of remote reactive streams. With RxTender, inter-process and inter-machine communication with reactive streams is very easy.
See the [documentation](http://rxtender.org/doc/latest/index.html) for more information.
Try the [getting started](http://rxtender.org/doc/latest/get_started/index.html) tutorial to see how to use it.
1 maintainer
Metadata
1 maintainer
Release files for rxtender 0.4.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 | |
|---|---|---|---|---|
| rxtender-0.4.0.zip | 7.4 kB | Without provenance | Details |
Release files / rxtender-0.4.0.zip
| Download URL | rxtender-0.4.0.zip |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d3c527251a1285018c0e0f3fc17359741b3360ac3e2ceedd84121fb43cf97ee
|
|
BLAKE2b-256 checksum How to use checksums |
1bade50110951349c28df5a447125cc31cb56b6a4875dc8e5e80ecbfc969014d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rxtender 0.4.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.
