Rename pyvortex to vortex-python (#3377)

This has been annoying me for a while...

The PyPi package is now called vortex-data, and this is largely a
regular Rust crate. So let's stick with the same naming convention as
the others (e.g. vortex-jni)

---------

Signed-off-by: Nicholas Gates <[email protected]>

Author: gatesn

.github/workflows/ci.yml

@@ -79,15 +79,15 @@ jobs:
           sync: false
 
       # Ensure the stub files are up-to-date with the public API of the native module.
-      - name: Stubtest - PyVortex
+      - name: Stubtest - Vortex
         run: |
           uv run --isolated --all-packages stubtest vortex._lib --allowlist python/vortex/_lib/mypy.allowlist
-        working-directory: pyvortex/
+        working-directory: vortex-python/
 
-      - name: Pytest - PyVortex
+      - name: Pytest - Vortex
         run: |
           uv run --isolated --all-packages pytest --benchmark-disable test/
-        working-directory: pyvortex/
+        working-directory: vortex-python/
 
       - name: Doctest - PyVortex
         run: |
@@ -120,7 +120,7 @@ jobs:
           else
             echo "Generated two files"
           fi
-        working-directory: pyvortex/
+        working-directory: vortex-python/
 
   rust-docs:
     name: "Rust (docs)"
@@ -140,7 +140,7 @@ jobs:
         run: |
           cargo doc --no-deps
           # nextest doesn't support doc tests, so we run it here
-          cargo test --doc --workspace --all-features --exclude pyvortex --exclude vortex-jni --exclude vortex-ffi --exclude xtask --no-fail-fast
+          cargo test --doc --workspace --all-features --exclude vortex-python --exclude vortex-jni --exclude vortex-ffi --exclude xtask --no-fail-fast
 
   build-rust:
     name: "Rust build (${{matrix.config.name}})"
@@ -391,7 +391,7 @@ jobs:
             --exclude vortex-datafusion \
             --exclude vortex-tui \
             --exclude vortex-fuzz \
-            --exclude pyvortex \
+            --exclude vortex-python \
             --exclude xtask \
             --workspace \
             --profile bench

.github/workflows/publish.yml

@@ -30,7 +30,7 @@ jobs:
         run: |
           cargo publish -Z package-workspace --allow-dirty --workspace \
           --exclude bench-vortex \
-          --exclude pyvortex \
+          --exclude vortex-python \
           --exclude vortex-duckdb \
           --exclude vortex-ffi \
           --exclude vortex-fuzz \
@@ -89,7 +89,7 @@ jobs:
             ${{ (matrix.target.os == 'ubuntu' && '--zig') || '' }}
             --compatibility manylinux2014
             --release
-            --manifest-path pyvortex/Cargo.toml
+            --manifest-path vortex-python/Cargo.toml
             --out dist
             --interpreter python3.11
         env:

CLAUDE.md

@@ -1,6 +1,6 @@
 # Development Guidelines
 
-* project is a monorepo Rust workspace, java bindings in `/java`, python bindings in `/pyvortex`
+* project is a monorepo Rust workspace, java bindings in `/java`, python bindings in `/vortex-python`
 * run `cargo build -p` to build a specific crate
 * use `cargo clippy --all-targets --all-features` to make sure a project is free of lint issues
 
@@ -15,7 +15,7 @@
 * More exotic compressed encodings live in the crates inside of `/encodings/*`
 * File IO is defined in `vortex-file`. It uses the concept of a `LayoutReader` defined
   in `vortex-layout` crate.
-* `/pyvortex` contains the python bindings. rst flavored docs for the project are in `/docs`
+* `/vortex-python` contains the python bindings. rst flavored docs for the project are in `/docs`
 
 # Code Style
 
@@ -24,4 +24,3 @@
   or cheap non-zero-cost abstractions.
 * Every new public API definition must have a doc comment. Examples are nice to have but not
   strictly required.
-

Cargo.lock

@@ -3,7 +3,6 @@ members = [
     "bench-vortex",
     "encodings/*",
     "fuzz",
-    "pyvortex",
     "vortex",
     "vortex-array",
     "vortex-btrblocks",
@@ -23,6 +22,7 @@ members = [
     "vortex-mask",
     "vortex-metrics",
     "vortex-proto",
+    "vortex-python",
     "vortex-scalar",
     "vortex-tui",
     "xtask",

Cargo.toml

@@ -2,11 +2,11 @@
 
 ## Building
 
-First, you must compile the pyvortex Rust code into a native library because the Python package
+First, you must compile the vortex-python Rust code into a native library because the Python package
 inherits some of its doc strings from Rust docstrings:
 
 ```
-cd ../pyvortex && uv run maturin develop
+cd ../vortex-python && uv run maturin develop
 ```
 
 Build the Vortex docs:

docs/README.md

@@ -32,7 +32,7 @@ dev-dependencies = [
 ]
 
 [tool.uv.workspace]
-members = ["pyvortex", "docs"]
+members = ["vortex-python", "docs"]
 
 [tool.uv.sources]
 vortex-data = { workspace = true }