concurrent-c-node 0.6.0__tar.gz → 0.7.0__tar.gz

{concurrent_c_node-0.6.0 → concurrent_c_node-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: concurrent-c-node
-Version: 0.6.0
+Version: 0.7.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
@@ -129,8 +129,8 @@ 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).)
+tier: `cc_js_new(false, &a)` boots libnode *inside* your CC program — see
+[`examples/js/jsdemo.shcc`](https://github.com/sreekotay/concurrent-c/blob/main/examples/js/jsdemo.shcc).)
 
 ## Publishing
 

{concurrent_c_node-0.6.0 → concurrent_c_node-0.7.0}/README.md

@@ -118,8 +118,8 @@ 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).)
+tier: `cc_js_new(false, &a)` boots libnode *inside* your CC program — see
+[`examples/js/jsdemo.shcc`](https://github.com/sreekotay/concurrent-c/blob/main/examples/js/jsdemo.shcc).)
 
 ## Publishing
 

{concurrent_c_node-0.6.0 → concurrent_c_node-0.7.0}/cc_node/broker.cjs

@@ -10,7 +10,11 @@
  * Python callable crosses as {$f: id}; invoking it sends a nested `cb`
  * request and BLOCKS on a synchronous read for the answer — legal
  * because the protocol is strictly alternating, so nothing else can be
- * in flight.  stdin EOF is the host vanishing: exit. */
+ * in flight.  stdin EOF is the host vanishing: exit.
+ *
+ * cc/include/ccc/script/js.cch embeds this file verbatim (the CC
+ * isolated tier speaks the same wire); js_iso_smoke pins the two
+ * byte-identical, so an edit here must land there too. */
 'use strict';
 
 const fs = require('fs');

{concurrent_c_node-0.6.0 → concurrent_c_node-0.7.0}/concurrent_c_node.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: concurrent-c-node
-Version: 0.6.0
+Version: 0.7.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
@@ -129,8 +129,8 @@ 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).)
+tier: `cc_js_new(false, &a)` boots libnode *inside* your CC program — see
+[`examples/js/jsdemo.shcc`](https://github.com/sreekotay/concurrent-c/blob/main/examples/js/jsdemo.shcc).)
 
 ## Publishing
 

{concurrent_c_node-0.6.0 → concurrent_c_node-0.7.0}/pyproject.toml

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