metrust 0.4.1__tar.gz → 0.4.2__tar.gz

{metrust-0.4.1 → metrust-0.4.2}/Cargo.lock

@@ -802,7 +802,7 @@ dependencies = [
 
 [[package]]
 name = "metrust-py"
-version = "0.4.1"
+version = "0.4.2"
 dependencies = [
  "metrust",
  "numpy",

{metrust-0.4.1 → metrust-0.4.2}/Cargo.toml

@@ -8,7 +8,7 @@ license = "MIT"
 
 [package]
 name = "metrust-py"
-version = "0.4.1"
+version = "0.4.2"
 edition.workspace = true
 description = "Python bindings for metrust, a Rust-powered MetPy-compatible calculation layer"
 readme = "README.md"

{metrust-0.4.1 → metrust-0.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: metrust
-Version: 0.4.1
+Version: 0.4.2
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Science/Research
 Classifier: License :: OSI Approved :: MIT License
@@ -54,7 +54,7 @@ pip install metrust metpy
 
 ## What It Does
 
-metrust implements every function in `metpy.calc` with a Rust backend compiled via PyO3. The Python API is designed for MetPy-compatible units, return types, and common calling conventions, without claiming byte-for-byte parity with every historical MetPy wrapper signature:
+metrust implements every function in `metpy.calc` with a Rust backend compiled via PyO3. The Python API now matches MetPy's public `metpy.calc` signatures and is designed for MetPy-compatible units, return types, and runtime behavior on the shared calculation surface:
 
 ```python
 import numpy as np
@@ -231,7 +231,7 @@ These forward to MetPy when installed:
 - `metrust.xarray` (xarray accessor)
 - `metrust.io.Level2File` (NEXRAD Level II)
 
-Core `metrust.calc` is native Rust by default with no MetPy dependency. The optional `met-cu` backend is an explicit accelerator, not a requirement.
+Core `metrust.calc` stays native Rust by default with no required MetPy dependency. A small parity-sensitive subset may delegate to MetPy when it is installed; otherwise those paths still fall back to local metrust implementations. The optional `met-cu` backend is an explicit accelerator, not a requirement.
 
 ## Examples
 

{metrust-0.4.1 → metrust-0.4.2}/README.md

@@ -30,7 +30,7 @@ pip install metrust metpy
 
 ## What It Does
 
-metrust implements every function in `metpy.calc` with a Rust backend compiled via PyO3. The Python API is designed for MetPy-compatible units, return types, and common calling conventions, without claiming byte-for-byte parity with every historical MetPy wrapper signature:
+metrust implements every function in `metpy.calc` with a Rust backend compiled via PyO3. The Python API now matches MetPy's public `metpy.calc` signatures and is designed for MetPy-compatible units, return types, and runtime behavior on the shared calculation surface:
 
 ```python
 import numpy as np
@@ -207,7 +207,7 @@ These forward to MetPy when installed:
 - `metrust.xarray` (xarray accessor)
 - `metrust.io.Level2File` (NEXRAD Level II)
 
-Core `metrust.calc` is native Rust by default with no MetPy dependency. The optional `met-cu` backend is an explicit accelerator, not a requirement.
+Core `metrust.calc` stays native Rust by default with no required MetPy dependency. A small parity-sensitive subset may delegate to MetPy when it is installed; otherwise those paths still fall back to local metrust implementations. The optional `met-cu` backend is an explicit accelerator, not a requirement.
 
 ## Examples
 

{metrust-0.4.1 → metrust-0.4.2}/docs/compatibility.md

@@ -10,9 +10,9 @@ in Rust versus what it delegates to MetPy.
 metrust is a MetPy-compatible calculation layer for `metpy.calc`, backed by a compiled Rust
 engine (`_metrust`).  The compatibility model has three tiers:
 
-Function coverage in the tables below is a functionality matrix, not a guarantee of byte-for-byte
-signature parity with every historical MetPy calling convention. The compatibility tests cover the
-most common wrapper forms and explicit regression cases.
+Function coverage in the tables below is a functionality matrix. Public `metpy.calc` signatures now
+match MetPy, and the compatibility tests cover explicit runtime regression cases on the shared
+calculation surface.
 
 | Tier | Description |
 |------|-------------|

{metrust-0.4.1 → metrust-0.4.2}/docs/guides/migration.md

@@ -19,7 +19,7 @@ from metrust.units import units
 
 That is the entire change for most code. Every function in `metrust.calc`
 accepts the same Pint Quantity inputs and returns Pint Quantity outputs, using
-the same function names and the same positional/keyword signatures as MetPy.
+the same function names and the same public positional/keyword signatures as MetPy.
 
 A project-wide find-and-replace from `metpy.` to `metrust.` is usually
 sufficient. The table below shows the namespace mapping:

{metrust-0.4.1 → metrust-0.4.2}/docs/index.md

@@ -53,7 +53,7 @@ The surface is identical. Under the hood, every calculation runs through compile
 
 ### 150/150 MetPy Calc Functions (Plus 36 Extras)
 
-Every function in `metpy.calc` has a metrust equivalent -- 100% API coverage. Plus 36 additional functions MetPy doesn't have (grid composites, fire weather indices, and more). The entire `metrust.calc` module is backed by Rust -- no MetPy dependency, no Python fallback.
+Every function in `metpy.calc` has a metrust equivalent -- 100% API coverage. Plus 36 additional functions MetPy doesn't have (grid composites, fire weather indices, and more). The calculation layer is Rust-backed by default, with a small parity-sensitive subset optionally delegating to MetPy when it is installed.
 Coverage spans the core of operational meteorology:
 
 - **Thermodynamics** -- potential temperature, equivalent potential temperature, virtual temperature, wet-bulb temperature, LCL, LFC, EL, CAPE/CIN, parcel profiles, precipitable water, thickness hydrostatic, stability indices
@@ -149,8 +149,8 @@ All `metrust.calc` functions compile to native machine code through the Rust too
 
 ### No MetPy Dependency for Calculations
 
-`pip install metrust` pulls in **only** NumPy and Pint. The entire calculation layer is self-contained.
-MetPy is never imported, loaded, or called for any `metrust.calc` function.
+`pip install metrust` pulls in **only** NumPy and Pint. The calculation layer stays self-contained by default.
+A small parity-sensitive subset of `metrust.calc` can delegate to MetPy when MetPy is installed, but the default path remains the Rust backend.
 
 ### Optional MetPy for Plots, xarray, and Level 2
 
@@ -158,7 +158,7 @@ A handful of surfaces intentionally delegate to MetPy when it is installed:
 
 | Surface | Behavior |
 |---|---|
-| `metrust.calc` | 100% native Rust. No MetPy fallback. |
+| `metrust.calc` | Native Rust by default, with limited optional MetPy delegation on a few parity-sensitive paths. |
 | `metrust.io.Level2File` | Forwards to MetPy's Level 2 reader when available. |
 | `metrust.plots` | Forwards to `metpy.plots`. |
 | `metrust.xarray` | Forwards to `metpy.xarray`. |

{metrust-0.4.1 → metrust-0.4.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "maturin"
 
 [project]
 name = "metrust"
-version = "0.4.1"
+version = "0.4.2"
 description = "Rust-powered MetPy-compatible calculation layer with optional GPU acceleration"
 requires-python = ">=3.9"
 license = {text = "MIT"}