publish as catena-corpus on PyPI and npm

Both registries already have a `catena`: an HPE blockchain client on PyPI,
and a JavaScript OOP wrapper at 2.2.0 on npm. Neither is going anywhere, so
the distributions take a name that is free on both.

The Python import is unaffected — a distribution name and a module name are
independent there, so `pip install catena-corpus` still gives `import
catena`, and nothing in the examples or the bindings changes. On npm the
package name is the import specifier, so that one does change: `import
{ chunkMarkdown } from "catena-corpus"`.

The crates keep their own names. `catena` is free on crates.io.
This commit is contained in:
funkpower
2026-09-21 08:15:26 -04:00
parent 58be244478
commit 57bc4356ab
9 changed files with 16 additions and 16 deletions
+2 -2
View File
@@ -77,8 +77,8 @@ callable in process from three languages:
| | Install | Import |
|---|---|---|
| **Python** | `pip install catena` | `import catena` |
| **JavaScript** | `npm install catena` | `import { chunkMarkdown } from "catena"` |
| **Python** | `pip install catena-corpus` | `import catena` |
| **JavaScript** | `npm install catena-corpus` | `import { chunkMarkdown } from "catena-corpus"` |
| **C** | build the `capi` feature | `#include <catena.h>` |
```python