concurrent-c-node 0.23.1__tar.gz → 0.23.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (19) hide show
  1. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/PKG-INFO +8 -1
  2. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/README.md +7 -0
  3. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/__init__.py +1 -1
  4. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/concurrent_c_node.egg-info/PKG-INFO +8 -1
  5. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/pyproject.toml +1 -1
  6. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/benchmarks/__init__.py +0 -0
  7. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/benchmarks/multi_domain.py +0 -0
  8. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/benchmarks/vs_alts.py +0 -0
  9. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/broker.cjs +0 -0
  10. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/examples/__init__.py +0 -0
  11. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/examples/bench_wire.py +0 -0
  12. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/examples/use_node.py +0 -0
  13. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/magics.py +0 -0
  14. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/cc_node/stdio_line.cjs +0 -0
  15. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/concurrent_c_node.egg-info/SOURCES.txt +0 -0
  16. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/concurrent_c_node.egg-info/dependency_links.txt +0 -0
  17. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/concurrent_c_node.egg-info/requires.txt +0 -0
  18. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/concurrent_c_node.egg-info/top_level.txt +0 -0
  19. {concurrent_c_node-0.23.1 → concurrent_c_node-0.23.2}/setup.cfg +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: concurrent-c-node
3
- Version: 0.23.1
3
+ Version: 0.23.2
4
4
  Summary: JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime.
5
5
  License: MIT
6
6
  Project-URL: Repository, https://github.com/sreekotay/concurrent-c
@@ -18,6 +18,13 @@ Requires-Dist: ipython>=7; extra == "jupyter"
18
18
  Call Node (and npm packages) from Python.
19
19
  Native types, exceptions, callbacks, and async all cross the boundary.
20
20
 
21
+ ## Why use this
22
+
23
+ Call real Node from Python — `require`, native addons, npm — not a JS
24
+ engine in-process. One child, shm for bulk, `from cc_node import require`
25
+ in Jupyter/Colab with no `%load_ext`. pythonia is the packaged peer; this
26
+ is faster on the wire and honest about bulk and callbacks.
27
+
21
28
  Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
22
29
  strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
23
30
  with your host C compiler. (This bridge itself is pure Python stdlib —
@@ -3,6 +3,13 @@
3
3
  Call Node (and npm packages) from Python.
4
4
  Native types, exceptions, callbacks, and async all cross the boundary.
5
5
 
6
+ ## Why use this
7
+
8
+ Call real Node from Python — `require`, native addons, npm — not a JS
9
+ engine in-process. One child, shm for bulk, `from cc_node import require`
10
+ in Jupyter/Colab with no `%load_ext`. pythonia is the packaged peer; this
11
+ is faster on the wire and honest about bulk and callbacks.
12
+
6
13
  Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
7
14
  strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
8
15
  with your host C compiler. (This bridge itself is pure Python stdlib —
@@ -43,7 +43,7 @@ __all__ = [
43
43
  "JsError", "JsHandle",
44
44
  "load_ipython_extension", "unload_ipython_extension", "__version__",
45
45
  ]
46
- __version__ = "0.23.1"
46
+ __version__ = "0.23.2"
47
47
 
48
48
  _NO_NODE = (
49
49
  "cc-node: no node executable (install Node, or set CC_NODE_BIN). "
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: concurrent-c-node
3
- Version: 0.23.1
3
+ Version: 0.23.2
4
4
  Summary: JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime.
5
5
  License: MIT
6
6
  Project-URL: Repository, https://github.com/sreekotay/concurrent-c
@@ -18,6 +18,13 @@ Requires-Dist: ipython>=7; extra == "jupyter"
18
18
  Call Node (and npm packages) from Python.
19
19
  Native types, exceptions, callbacks, and async all cross the boundary.
20
20
 
21
+ ## Why use this
22
+
23
+ Call real Node from Python — `require`, native addons, npm — not a JS
24
+ engine in-process. One child, shm for bulk, `from cc_node import require`
25
+ in Jupyter/Colab with no `%load_ext`. pythonia is the packaged peer; this
26
+ is faster on the wire and honest about bulk and callbacks.
27
+
21
28
  Part of [Concurrent-C](https://github.com/sreekotay/concurrent-c) — a
22
29
  strict C11-superset preprocessor: `.ccs` lowers to plain C and compiles
23
30
  with your host C compiler. (This bridge itself is pure Python stdlib —
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "concurrent-c-node"
7
- version = "0.23.1"
7
+ version = "0.23.2"
8
8
  description = "JavaScript and npm packages from Python over the Concurrent-C bridge: one spawned Node child per domain, host-controlled lifetime."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.8"