PyPI - spatial-computing - Versions diffs - 0.6.0__tar.gz → 0.6.1__tar.gz - Mend

spatial-computing 0.6.0tar.gz → 0.6.1tar.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 (73) hide show

{spatial_computing-0.6.0/spatial_computing.egg-info → spatial_computing-0.6.1}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spatial-computing
-Version: 0.6.0
+Version: 0.6.1
 Summary: Spatial Computing: open-source infrastructure efficiency toolkit. Measure, decide, prove (compute, tiered memory, runtime routing, hybrid quantum language)
 Author: Spatial Computing contributors
 License-Expression: Apache-2.0
@@ -37,7 +37,7 @@ Dynamic: license-file
 Spatial Computing chooses where and how a workload should run from measurements, and claims a gain only when it is measured. It does not add RAM, cores or GPUs: it compares execution strategies on the hardware you have, trades one resource for another in numbers, and says plainly what it cannot do.
-> **Status: v0.6.0, early-stage open-source toolkit.** Everything here was built and measured on a single 2017 MacBook Pro (Intel i7-7660U, 2 cores, 16 GB). Nothing has been proven on a second machine, a data-center GPU or a real quantum computer. See [Limitations](docs/LIMITATIONS.md) and the [site](https://spatial-computing-ecru.vercel.app).
+> **Status: v0.6.1, early-stage open-source toolkit.** Everything here was built and measured on a single 2017 MacBook Pro (Intel i7-7660U, 2 cores, 16 GB). Nothing has been proven on a second machine, a data-center GPU or a real quantum computer. See [Limitations](docs/LIMITATIONS.md) and the [site](https://spatial-computing-ecru.vercel.app).
 [Français](README.fr.md)

{spatial_computing-0.6.0 → spatial_computing-0.6.1}/README.md RENAMED Viewed

@@ -4,7 +4,7 @@
 Spatial Computing chooses where and how a workload should run from measurements, and claims a gain only when it is measured. It does not add RAM, cores or GPUs: it compares execution strategies on the hardware you have, trades one resource for another in numbers, and says plainly what it cannot do.
-> **Status: v0.6.0, early-stage open-source toolkit.** Everything here was built and measured on a single 2017 MacBook Pro (Intel i7-7660U, 2 cores, 16 GB). Nothing has been proven on a second machine, a data-center GPU or a real quantum computer. See [Limitations](docs/LIMITATIONS.md) and the [site](https://spatial-computing-ecru.vercel.app).
+> **Status: v0.6.1, early-stage open-source toolkit.** Everything here was built and measured on a single 2017 MacBook Pro (Intel i7-7660U, 2 cores, 16 GB). Nothing has been proven on a second machine, a data-center GPU or a real quantum computer. See [Limitations](docs/LIMITATIONS.md) and the [site](https://spatial-computing-ecru.vercel.app).
 [Français](README.fr.md)

{spatial_computing-0.6.0 → spatial_computing-0.6.1}/pyproject.toml RENAMED Viewed

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "spatial-computing"
-version = "0.6.0"
+version = "0.6.1"
 description = "Spatial Computing: open-source infrastructure efficiency toolkit. Measure, decide, prove (compute, tiered memory, runtime routing, hybrid quantum language)"
 readme = "README.md"
 license = "Apache-2.0"

{spatial_computing-0.6.0 → spatial_computing-0.6.1}/spatial/__init__.py RENAMED Viewed

@@ -3,4 +3,4 @@
 Status of every engine is declared in spatial.core.registry and must be backed
 by a test or benchmark before being set to OPERATIONAL.
 """
-__version__ = "0.6.0"
+__version__ = "0.6.1"

{spatial_computing-0.6.0 → spatial_computing-0.6.1}/spatial/q/backends/__init__.py RENAMED Viewed

@@ -147,9 +147,9 @@ class QpuBackend(Backend):
             raise BackendUnavailable(f"IBM Quantum refused the account: {type(e).__name__}: {str(e)[:200]}")
     def sample(self, c, shots, seed=None):
+        svc = self._service()                      # raises BackendUnavailable first if the package/token is missing
         from qiskit import transpile
         from qiskit_ibm_runtime import SamplerV2
-        svc = self._service()
         try:
             backend = svc.least_busy(operational=True, simulator=False, min_num_qubits=c.n_qubits)
         except Exception as e:

{spatial_computing-0.6.0 → spatial_computing-0.6.1/spatial_computing.egg-info}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spatial-computing
-Version: 0.6.0
+Version: 0.6.1
 Summary: Spatial Computing: open-source infrastructure efficiency toolkit. Measure, decide, prove (compute, tiered memory, runtime routing, hybrid quantum language)
 Author: Spatial Computing contributors
 License-Expression: Apache-2.0
@@ -37,7 +37,7 @@ Dynamic: license-file
 Spatial Computing chooses where and how a workload should run from measurements, and claims a gain only when it is measured. It does not add RAM, cores or GPUs: it compares execution strategies on the hardware you have, trades one resource for another in numbers, and says plainly what it cannot do.
-> **Status: v0.6.0, early-stage open-source toolkit.** Everything here was built and measured on a single 2017 MacBook Pro (Intel i7-7660U, 2 cores, 16 GB). Nothing has been proven on a second machine, a data-center GPU or a real quantum computer. See [Limitations](docs/LIMITATIONS.md) and the [site](https://spatial-computing-ecru.vercel.app).
+> **Status: v0.6.1, early-stage open-source toolkit.** Everything here was built and measured on a single 2017 MacBook Pro (Intel i7-7660U, 2 cores, 16 GB). Nothing has been proven on a second machine, a data-center GPU or a real quantum computer. See [Limitations](docs/LIMITATIONS.md) and the [site](https://spatial-computing-ecru.vercel.app).
 [Français](README.fr.md)