fix(py): a 0-d integer array indexes like an int
ds[np.array(1)] went down the index-list path, where tolist() returns a scalar and extracting a list of indices raised a confusing TypeError. h5py treats it as an integer index; so do we now. The h5py comparison keys include 0-d arrays (signed and unsigned) on each axis; they failed before. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This commit is contained in:
@@ -91,6 +91,9 @@
|
||||
API: `File::dataset_at(address)` opens a dataset without resolving a
|
||||
path. libhdf5's `h5stat_newgrat.h5` (35001 members in the root): listing
|
||||
takes 0.03 s and 2000 opens 1 ms (h5py: 0.022 s).
|
||||
- **`ds[np.array(1)]` is an integer index**, as in h5py; a 0-d integer
|
||||
array went down the index-list path and raised a confusing `TypeError`.
|
||||
The h5py comparison keys now include 0-d arrays on every axis.
|
||||
- **CI builds and tests the Python package.** It was excluded from CI.
|
||||
`scripts/ci-test.sh` now lints `clawhdf5-py`, builds the wheel with
|
||||
maturin, unpacks it under `target/` and runs the pytest suite; skipped
|
||||
|
||||
Reference in New Issue
Block a user