concurrent-c-node 0.4.0__tar.gz → 0.5.0__tar.gz

{concurrent_c_node-0.4.0 → concurrent_c_node-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: concurrent-c-node
-Version: 0.4.0
+Version: 0.5.0
 Summary: JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime.
 License: MIT
 Project-URL: Repository, https://github.com/sreekotay/concurrent-c
@@ -17,6 +17,10 @@ Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
 strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
 with your host C compiler.  (This bridge itself is pure Python.)
 
+Map of the three boundaries (CC hosts Python, native modules, this
+package bridge):
+[JS / Python interop](https://github.com/sreekotay/concurrent-c/blob/main/docs/js-py-modules.md).
+
 ```python
 import cc_node
 
@@ -119,6 +123,10 @@ And *which packages* it sees is the working directory's
 Run Python in your project, get your project's packages: `npm install`
 next to your program is the whole setup.
 
+(Writing Concurrent-C itself rather than Python?  There is a zero-IPC
+tier: `cc_js_host_new(&a)` boots libnode *inside* your CC program — see
+[`examples/recipe_js_host.ccs`](https://github.com/sreekotay/concurrent-c/blob/main/examples/recipe_js_host.ccs).)
+
 ## Publishing
 
 From the Concurrent-C repo root (packs this wheel and the npm sibling):
@@ -153,10 +161,12 @@ A worked tour (builtin Node modules, chains, callbacks, thenables,
 buffers — no npm install needed):
 `python -m cc_node.examples.use_node`.
 
-Adversarial multi-child storm (fanout, callback blizzard, shm hail,
-teardown derby): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
-— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` for bigger N; latency demos
-stay in `cc_node/examples/`).
+Adversarial multi-child storm (fanout, abort inject, mixed concurrent,
+handle-leak / RSS soaks): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
+— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` / `soak` for bigger N).
+Mode catalog + status:
+[`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md)
+(latency demos stay in `cc_node/examples/`).
 
 And when the hot path is YOUR code rather than an npm package, skip the
 wire entirely: a page of Concurrent-C (or C) exports as a native module

{concurrent_c_node-0.4.0 → concurrent_c_node-0.5.0}/README.md

@@ -6,6 +6,10 @@ Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
 strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
 with your host C compiler.  (This bridge itself is pure Python.)
 
+Map of the three boundaries (CC hosts Python, native modules, this
+package bridge):
+[JS / Python interop](https://github.com/sreekotay/concurrent-c/blob/main/docs/js-py-modules.md).
+
 ```python
 import cc_node
 
@@ -108,6 +112,10 @@ And *which packages* it sees is the working directory's
 Run Python in your project, get your project's packages: `npm install`
 next to your program is the whole setup.
 
+(Writing Concurrent-C itself rather than Python?  There is a zero-IPC
+tier: `cc_js_host_new(&a)` boots libnode *inside* your CC program — see
+[`examples/recipe_js_host.ccs`](https://github.com/sreekotay/concurrent-c/blob/main/examples/recipe_js_host.ccs).)
+
 ## Publishing
 
 From the Concurrent-C repo root (packs this wheel and the npm sibling):
@@ -142,10 +150,12 @@ A worked tour (builtin Node modules, chains, callbacks, thenables,
 buffers — no npm install needed):
 `python -m cc_node.examples.use_node`.
 
-Adversarial multi-child storm (fanout, callback blizzard, shm hail,
-teardown derby): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
-— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` for bigger N; latency demos
-stay in `cc_node/examples/`).
+Adversarial multi-child storm (fanout, abort inject, mixed concurrent,
+handle-leak / RSS soaks): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
+— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` / `soak` for bigger N).
+Mode catalog + status:
+[`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md)
+(latency demos stay in `cc_node/examples/`).
 
 And when the hot path is YOUR code rather than an npm package, skip the
 wire entirely: a page of Concurrent-C (or C) exports as a native module

{concurrent_c_node-0.4.0 → concurrent_c_node-0.5.0}/cc_node/__init__.py

@@ -27,7 +27,7 @@ import os
 import subprocess
 
 __all__ = ["create", "JsError", "JsHandle", "__version__"]
-__version__ = "0.2.0"
+__version__ = "0.4.0"
 
 # Typed buffers cross as typed arrays; big ones spill through shared
 # memory (tmpfs where available) — one memcpy per side, receiver

{concurrent_c_node-0.4.0 → concurrent_c_node-0.5.0}/concurrent_c_node.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: concurrent-c-node
-Version: 0.4.0
+Version: 0.5.0
 Summary: JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime.
 License: MIT
 Project-URL: Repository, https://github.com/sreekotay/concurrent-c
@@ -17,6 +17,10 @@ Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
 strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
 with your host C compiler.  (This bridge itself is pure Python.)
 
+Map of the three boundaries (CC hosts Python, native modules, this
+package bridge):
+[JS / Python interop](https://github.com/sreekotay/concurrent-c/blob/main/docs/js-py-modules.md).
+
 ```python
 import cc_node
 
@@ -119,6 +123,10 @@ And *which packages* it sees is the working directory's
 Run Python in your project, get your project's packages: `npm install`
 next to your program is the whole setup.
 
+(Writing Concurrent-C itself rather than Python?  There is a zero-IPC
+tier: `cc_js_host_new(&a)` boots libnode *inside* your CC program — see
+[`examples/recipe_js_host.ccs`](https://github.com/sreekotay/concurrent-c/blob/main/examples/recipe_js_host.ccs).)
+
 ## Publishing
 
 From the Concurrent-C repo root (packs this wheel and the npm sibling):
@@ -153,10 +161,12 @@ A worked tour (builtin Node modules, chains, callbacks, thenables,
 buffers — no npm install needed):
 `python -m cc_node.examples.use_node`.
 
-Adversarial multi-child storm (fanout, callback blizzard, shm hail,
-teardown derby): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
-— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` for bigger N; latency demos
-stay in `cc_node/examples/`).
+Adversarial multi-child storm (fanout, abort inject, mixed concurrent,
+handle-leak / RSS soaks): [`stress/bridge/`](https://github.com/sreekotay/concurrent-c/tree/main/stress/bridge)
+— `./stress/bridge/run.sh` (`CHAOS_SCALE=full` / `soak` for bigger N).
+Mode catalog + status:
+[`bridge_stress.md`](https://github.com/sreekotay/concurrent-c/blob/main/stress/bridge/bridge_stress.md)
+(latency demos stay in `cc_node/examples/`).
 
 And when the hot path is YOUR code rather than an npm package, skip the
 wire entirely: a page of Concurrent-C (or C) exports as a native module

{concurrent_c_node-0.4.0 → concurrent_c_node-0.5.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "concurrent-c-node"
-version = "0.4.0"
+version = "0.5.0"
 description = "JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime."
 readme = "README.md"
 requires-python = ">=3.8"