==============
A pure Python implementation of ribbon-bridge, an RPC framework. Read more about
ribbon-bridge at http://github.com/BaroboRobotics/ribbon-bridge .
Requirements
------------
Ribbon bridge uses asyncio for asynchronous remote procedure calls, and thus
requires Python 3.5 or above.
Internally, it uses Google Protocol Buffers for data serialization, and thus
requires protobuf-v3.0.0b2 or later.
Usage
-----
The basic strategy is:
1. Design the procedure call interface with Google Protobuf. Each callable
remote procedure is represented by a nested protobuf message. In order to
be a valid callable remote procedure, the message must have sub-messages
named "In" and "Result". For instance, to implement a remote procedure
called "foo" which takes a float and returns and integer, you would
have the following entry in a .proto file.
message foo {
message In {
float input = 1;
}
message Result {
int32 output = 1;
}
}
2. Use protoc to generate python files from the .proto files.
3. Create a Proxy object. The Proxy object will need a path to the Python
interface file generated by protoc and an asyncio event loop.
Metadata
Release files for PyRibbonBridge 0.1.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 | |
|---|---|---|---|---|
| PyRibbonBridge-0.1.2.tar.gz | 12.0 kB | Without provenance | Details |
Release files / PyRibbonBridge-0.1.2.tar.gz
| Download URL | PyRibbonBridge-0.1.2.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6159c18756761598fc8a0564cd08311b87f6b76ca4e1411d3b00d5712e6705aa
|
|
BLAKE2b-256 checksum How to use checksums |
4767f3c1f2c23b6da74b316eb0a6a2fb1d5492b97d985946a8a3a2f7de7c9b7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for PyRibbonBridge 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.