graphrefly 0.2.0__tar.gz → 0.3.0__tar.gz

{graphrefly-0.2.0 → graphrefly-0.3.0}/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 <!-- version list -->
 
+## v0.3.0 (2026-04-04)
+
+### Chores
+
+- Fix code pane
+  ([`a844d7f`](https://github.com/graphrefly/graphrefly-py/commit/a844d7f3e5d5a34169d67d668f0b9556888814e1))
+
+- Update readme and fix site
+  ([`dbcd4d1`](https://github.com/graphrefly/graphrefly-py/commit/dbcd4d11f878b77a3f4ab95ae359d528b1b073af))
+
+### Features
+
+- Fix website's contrast
+  ([`002ac99`](https://github.com/graphrefly/graphrefly-py/commit/002ac9988c9051bbbfc2c857a7259ff6f66e3def))
+
+
 ## v0.2.0 (2026-04-04)
 
 ### Features

{graphrefly-0.2.0 → graphrefly-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: graphrefly
-Version: 0.2.0
+Version: 0.3.0
 Summary: Reactive graph protocol for human + LLM co-operation. Composable nodes, glitch-free diamond resolution, two-phase push, durable streaming. Zero dependencies.
 Project-URL: Homepage, https://py.graphrefly.dev
 Project-URL: Repository, https://github.com/graphrefly/graphrefly-py
@@ -29,9 +29,9 @@ Description-Content-Type: text/markdown
 
 One primitive. Zero dependencies. Composable nodes with glitch-free diamond resolution, two-phase push propagation, durable streaming, and async runners for asyncio and trio.
 
-[![PyPI](https://img.shields.io/pypi/v/graphrefly-py?color=blue)](https://pypi.org/project/graphrefly-py/)
+[![PyPI](https://img.shields.io/pypi/v/graphrefly-py?color=blue)](https://pypi.org/project/graphrefly/)
 [![license](https://img.shields.io/github/license/graphrefly/graphrefly-py)](./LICENSE)
-[![Python](https://img.shields.io/pypi/pyversions/graphrefly-py)](https://pypi.org/project/graphrefly-py/)
+[![Python](https://img.shields.io/pypi/pyversions/graphrefly-py)](https://pypi.org/project/graphrefly/)
 
 [Docs](https://py.graphrefly.dev) | [Spec](https://py.graphrefly.dev/spec/) | [TypeScript](https://graphrefly.dev) | [API Reference](https://py.graphrefly.dev/api/)
 
@@ -40,7 +40,7 @@ One primitive. Zero dependencies. Composable nodes with glitch-free diamond reso
 ## Quick start
 
 ```bash
-pip install graphrefly-py
+pip install graphrefly
 ```
 
 ```python

{graphrefly-0.2.0 → graphrefly-0.3.0}/README.md

@@ -4,9 +4,9 @@
 
 One primitive. Zero dependencies. Composable nodes with glitch-free diamond resolution, two-phase push propagation, durable streaming, and async runners for asyncio and trio.
 
-[![PyPI](https://img.shields.io/pypi/v/graphrefly-py?color=blue)](https://pypi.org/project/graphrefly-py/)
+[![PyPI](https://img.shields.io/pypi/v/graphrefly-py?color=blue)](https://pypi.org/project/graphrefly/)
 [![license](https://img.shields.io/github/license/graphrefly/graphrefly-py)](./LICENSE)
-[![Python](https://img.shields.io/pypi/pyversions/graphrefly-py)](https://pypi.org/project/graphrefly-py/)
+[![Python](https://img.shields.io/pypi/pyversions/graphrefly-py)](https://pypi.org/project/graphrefly/)
 
 [Docs](https://py.graphrefly.dev) | [Spec](https://py.graphrefly.dev/spec/) | [TypeScript](https://graphrefly.dev) | [API Reference](https://py.graphrefly.dev/api/)
 
@@ -15,7 +15,7 @@ One primitive. Zero dependencies. Composable nodes with glitch-free diamond reso
 ## Quick start
 
 ```bash
-pip install graphrefly-py
+pip install graphrefly
 ```
 
 ```python

{graphrefly-0.2.0 → graphrefly-0.3.0}/docs/optimizations.md

@@ -125,6 +125,8 @@ Union-find over node identity merges components when nodes list dependencies at
 
 **Keep this section in sync with `graphrefly-ts/docs/optimizations.md` § Cross-language implementation notes** so you can open both files side by side.
 
+- **Storage & sink adapter pattern parity (Phase 5.2d, 2026-04-03):** All 5.2d sinks follow the same pattern in both TS and PY: duck-typed client protocols, `on_message` intercepting `DATA`, `SinkTransportError` for serialize/send failures. Buffered sinks (`to_clickhouse`, `to_s3`, `to_file`, `to_csv`) return a `BufferedSinkHandle` with `dispose()` + `flush()`. Per-record sinks (`to_postgres`, `to_mongo`, `to_loki`, `to_tempo`) return an unsubscribe callable. Checkpoint adapters (`checkpoint_to_s3`, `checkpoint_to_redis`) wire `graph.auto_checkpoint()`. PY uses `threading.Timer` for flush timers; TS uses `setTimeout`. PY `to_postgres` calls `client.execute(sql, params)` (psycopg2/3 style); TS calls `client.query(sql, params)` (pg style). PY `json.dumps` includes spaces after separators; TS `JSON.stringify` does not — NDJSON output is semantically equivalent but not byte-identical across languages.
+
 ### 1. Message type wire encoding
 
 | | |
@@ -319,6 +321,12 @@ Applies to `src/extra/adapters.ts` and `graphrefly.extra.adapters`. **Keep the t
 | **`fromPrometheus` / `fromClickHouseWatch` `signal` option** | `signal: AbortSignal` for external cancellation | No equivalent; uses `active[0]` flag on teardown | PY has no standard `AbortSignal`. External cancellation in PY is handled by unsubscribing (which triggers the cleanup/stop function). Both ports stop cleanly on teardown. |
 | **`SyslogMessage` field naming** | camelCase: `appName`, `procId`, `msgId` | snake_case: `app_name`, `proc_id`, `msg_id` | Language convention applied to output data structures. Each port follows its ecosystem's naming idiom. |
 | **`fromCSV` / `fromNDJSON` source type** | `AsyncIterable<string>` (async streams with chunk buffering) | `Iterable[str]` (sync iterators via threads) | PY uses threads for I/O concurrency; sync iterables are natural for `csv.reader` integration. TS uses async iteration for streaming I/O. |
+| **`PulsarConsumerLike` protocol** | `pulsar-client` JS shape: `receive()` returns Promise, `acknowledge(msg)` returns Promise, getter methods (`getData()`, `getTopicName()`, etc.) | `pulsar-client` PY shape: `receive()` blocking, `acknowledge(msg)` sync, attribute methods (`data()`, `topic_name()`, etc.) | Each port matches the native Pulsar client API for its ecosystem. TS uses async loop; PY uses threaded blocking loop. |
+| **`PulsarProducerLike.send()` call shape** | Single object: `send({data, partitionKey, properties})` | Positional + kwargs: `send(data, partition_key=..., properties=...)` | Matches respective native Pulsar client SDK calling conventions. |
+| **`PulsarMessage` field naming** | camelCase: `messageId`, `publishTime`, `eventTime` | snake_case: `message_id`, `publish_time`, `event_time` | Language convention applied to output data structures. |
+| **`NATSClientLike` protocol** | nats.js shape: `subscribe()` returns `AsyncIterable`, `publish(subject, data)` | Dual: sync iterable (threaded drain) or async iterable/coroutine (via `Runner`). Auto-detected at subscribe time. Optional `runner` kwarg. | TS uses native async iteration. PY auto-detects sync vs async subscriptions: sync uses threaded drain, async uses `resolve_runner().schedule()`. Both support queue groups. |
+| **`RabbitMQChannelLike` protocol** | amqplib shape: `consume(queue, callback)` returns `Promise<{consumerTag}>`, `cancel(tag)`, `ack(msg)`, `publish(exchange, routingKey, content)` | pika shape: `basic_consume(queue, on_message_callback, auto_ack)`, `start_consuming()`, `basic_ack(delivery_tag)`, `basic_publish(exchange, routing_key, body)` | Each port matches its ecosystem's dominant AMQP library. Pika requires `start_consuming()` to enter the event loop; amqplib's consume is promise-based. |
+| **`RabbitMQMessage` field naming** | camelCase: `routingKey`, `deliveryTag` | snake_case: `routing_key`, `delivery_tag` | Language convention applied to output data structures. |
 
 ---
 

{graphrefly-0.2.0 → graphrefly-0.3.0}/docs/roadmap.md

@@ -324,9 +324,9 @@ Connectors for the universal reduction layer (Phase 8). Each wraps an external p
 - [x] `from_redis_stream(client, key, opts)` / `to_redis_stream(source, client, key, opts)` — Redis Streams (duck-typed `RedisClientLike`).
 - [x] `from_csv(source, opts)` / `from_ndjson(source)` — `Iterable[str]` ingest for batch replay; threaded drain.
 - [x] `from_clickhouse_watch(client, query, opts)` — timer-driven query polling as reactive source.
-- [ ] `from_pulsar(consumer, topic, opts)` / `to_pulsar(source, producer, topic, opts)` — Apache Pulsar native client
-- [ ] `from_nats(consumer, subject, opts)` / `to_nats(source, client, subject, opts)` — NATS consumer/producer
-- [ ] `from_rabbitmq(channel, queue, opts)` / `to_rabbitmq(source, channel, exchange, opts)` — RabbitMQ consumer/producer
+- [x] `from_pulsar(consumer, opts)` / `to_pulsar(source, producer, opts)` — Apache Pulsar native client
+- [x] `from_nats(client, subject, opts)` / `to_nats(source, client, subject, opts)` — NATS consumer/producer
+- [x] `from_rabbitmq(channel, queue, opts)` / `to_rabbitmq(source, channel, exchange, opts)` — RabbitMQ consumer/producer
 
 ### 5.3c — Storage & sink adapters
 

{graphrefly-0.2.0 → graphrefly-0.3.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "graphrefly"
-version = "0.2.0"
+version = "0.3.0"
 description = "Reactive graph protocol for human + LLM co-operation. Composable nodes, glitch-free diamond resolution, two-phase push, durable streaming. Zero dependencies."
 readme = "README.md"
 license = "MIT"

{graphrefly-0.2.0 → graphrefly-0.3.0}/src/graphrefly/extra/__init__.py

@@ -11,9 +11,12 @@ from graphrefly.extra.adapters import (
     from_http,
     from_kafka,
     from_mcp,
+    from_nats,
     from_ndjson,
     from_otel,
     from_prometheus,
+    from_pulsar,
+    from_rabbitmq,
     from_redis_stream,
     from_statsd,
     from_syslog,
@@ -24,6 +27,9 @@ from graphrefly.extra.adapters import (
     parse_syslog,
     sse_frame,
     to_kafka,
+    to_nats,
+    to_pulsar,
+    to_rabbitmq,
     to_redis_stream,
     to_sse,
     to_websocket,
@@ -213,9 +219,12 @@ __all__ = [
     "from_http",
     "from_kafka",
     "from_mcp",
+    "from_nats",
     "from_ndjson",
     "from_otel",
     "from_prometheus",
+    "from_pulsar",
+    "from_rabbitmq",
     "from_redis_stream",
     "from_statsd",
     "from_syslog",
@@ -234,6 +243,9 @@ __all__ = [
     "throw_error",
     "to_array",
     "to_kafka",
+    "to_nats",
+    "to_pulsar",
+    "to_rabbitmq",
     "to_redis_stream",
     "sse_frame",
     "to_websocket",