Skip to main content

Invisibles

Transparent remote method invocation. Same object, same usage, different location.

What It Does

You have an object. You want to move it to another process, another node. The code that uses it doesn't change.

# Local
result = service.add(5, 3)
data = await service.fetch("key")

# Remote - identical
result = proxy.add(5, 3)
data = await proxy.fetch("key")

Sync methods stay sync. Async methods stay async. The proxy matches the remote object's API exactly.

Architecture

Two connection channels, each doing what it's good at:

  • Sync connection - reentrant serving pattern, handles sync methods and protocol operations
  • Async connection - message pump with asyncio futures, handles async methods natively

Both share a Protocol instance that manages boxing, dispatch, and proxy creation. See docs/architecture.md for details.

Key Concepts

  • Service - any Python object exposed remotely, no base class needed
  • Connection - per-client RPC channel (sync or async), wraps netkit transport
  • Proxy - client-side transparent handle, created automatically during unboxing
  • Protocol - shared RPC state: boxing, dispatch, object registry, proxy caching
  • Dispatcher - how sync method calls are run (inline, threaded, or shared)

Deployment Scenarios

Object type Clients Execution Setup
Sync, not thread-safe Single Serialized SyncServer + InlineDispatcher
Sync, not thread-safe Multiple Serialized SyncServer + SharedDispatcher
Sync, thread-safe Multiple Parallel SyncServer + ThreadedDispatcher
Async / Mixed Any Async on server loop SyncServer + AsyncDispatcher

See docs/scenarios.md for the full matrix.

Python Protocol Support

Works transparently over RPC:

  • Method calls (sync and async)
  • Attribute access
  • Iterators and generators (for x in proxy)
  • Async iterators (async for x in proxy)
  • Context managers (with proxy)
  • Async context managers (async with proxy)
  • Operator overloading (+, -, *, [], in, len, etc.)
  • Callable objects (proxy(args))
  • Exception propagation (including custom exception classes)
  • Nested objects (methods returning objects that are themselves proxied)

Docs

License

Apache-2.0 - See LICENSE.md

Metadata

Release files for invisibles-py 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for invisibles-py 0.1.1
File Size Uploaded
invisibles_py-0.1.1.tar.gz 97.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for invisibles-py 0.1.1
File Interpreter ABI Platform
invisibles_py-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 176.0 kB

Release files / invisibles_py-0.1.1.tar.gz

Download URL invisibles_py-0.1.1.tar.gz
Size 97.4 kB
Tags Source
SHA-256 checksum
How to use checksums
bcd169b568ac37446566845828ffbb7d17d0ad24b4ca46b233a4eff0174c21a1
BLAKE2b-256 checksum
How to use checksums
60edfec45e750b4dc81582a7aeff9b778fdabee97c96756b41bddb1d9d448253
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 6, 2026.

Transparency log

Release files / invisibles_py-0.1.1-py3-none-any.whl

Download URL invisibles_py-0.1.1-py3-none-any.whl
Size 78.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
96f7c5779239e5cd7eeec700b7468abd9c2d29097c106ada9d6f4fe729756fb1
BLAKE2b-256 checksum
How to use checksums
2cda6d595dd899549299c95f3fffbb1d480e3352d6a8f74e4947258001b1154c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 6, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.2

2 release files

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page