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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: concurrent-c-node
-Version: 0.4.0
+Version: 0.4.1
 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
@@ -119,6 +119,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):

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

@@ -108,6 +108,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):

{concurrent_c_node-0.4.0 → concurrent_c_node-0.4.1}/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.4.1}/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.4.1
 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
@@ -119,6 +119,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):

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

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "concurrent-c-node"
-version = "0.4.0"
+version = "0.4.1"
 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"