RPyC
This wiki is in the process of being archived due to lack of usage and the resources necessary to serve it — predominately to bots, crawlers, and LLM companies. Edits are discouraged.
Pages are preserved as they were at the time of archival. For current information, please visit python.org.
If a change to this archive is absolutely needed, requests can be made via the infrastructure@python.org mailing list.
RPyC (pronounced like are-pie-see), or Remote Python Call, is a transparent and symmetrical python library for remote procedure calls, clustering and distributed-computing. RPyC makes use of object-proxying, a technique that employs python's dynamic nature, to overcome the physical boundaries between processes and computers, so that remote objects can be manipulated as if they were local.
Features
- Transparent access to remote objects; program remotely as if working locally
- Symmetric protocol, where both the client and server can serve requests (which allows, for instance, to use callbacks)
- Synchronous and asynchronous invocation
- Platform-agnostic: 32/64 bit, little/big endian, Windows/Linux/Solaris/Mac… access objects across different architectures.
- Capability based security model
- Integration with TLS/SSL and inetd
Use cases
- Excels in testing environments
- Control multiple hardware or software platforms from a centralized point
- Access remote physical (hardware) resources transparently
- Distribute workload among multiple machines with ease
- Implement remote services (like SOAP or RMI) quickly and concisely (without the overhead and limitations of these technologies)