quantpad-data 0.8.0__tar.gz → 0.8.1__tar.gz

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: quantpad-data
-Version: 0.8.0
+Version: 0.8.1
 Summary: Official Python client for the QuantPad market-data API
 Project-URL: Documentation, https://api.quantpad.ai/external/docs
 Author: QuantPad
@@ -106,9 +106,8 @@ symbol it is. That is convenient until it is wrong, and when it is wrong it
 fails quietly — asking for a specific futures contract returns an empty frame
 that looks exactly like a coverage gap.
 
-`qpd.v2.Historical` removes the inference. It takes the same arguments as
-`databento.Historical`, so code written against Databento ports over by
-swapping the client:
+`qpd.v2.Historical` removes the inference. Every call names its dataset and
+symbology type explicitly, and every response reports the address it used:
 
 ```python
 import quantpad_data as qpd

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/README.md

@@ -84,9 +84,8 @@ symbol it is. That is convenient until it is wrong, and when it is wrong it
 fails quietly — asking for a specific futures contract returns an empty frame
 that looks exactly like a coverage gap.
 
-`qpd.v2.Historical` removes the inference. It takes the same arguments as
-`databento.Historical`, so code written against Databento ports over by
-swapping the client:
+`qpd.v2.Historical` removes the inference. Every call names its dataset and
+symbology type explicitly, and every response reports the address it used:
 
 ```python
 import quantpad_data as qpd

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "quantpad-data"
-version = "0.8.0"
+version = "0.8.1"
 description = "Official Python client for the QuantPad market-data API"
 readme = "README.md"
 requires-python = ">=3.10"

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/quantpad_data/__init__.py

@@ -198,7 +198,7 @@ def iter_l1_mbp1_df_chunks(symbol, start_ms, end_ms, chunksize=250_000,
 
 from . import cache  # noqa: E402  (submodule: on-disk cache for settled /v2)
 from . import lean  # noqa: E402  (submodule: LEAN backtesting data staging)
-from . import v2  # noqa: E402  (submodule: Databento-shaped explicit API)
+from . import v2  # noqa: E402  (submodule: explicit-address API)
 
 # Exported at the root as well as on ``v2``: the sandbox module reaches it
 # as ``qpd.Historical()``, and one spelling across both surfaces means

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/quantpad_data/client.py

@@ -84,7 +84,7 @@ V2_NOT_AVAILABLE = (
     "QuantPad support about /v2 access."
 )
 
-VERSION = "0.8.0"
+VERSION = "0.8.1"
 USER_AGENT = f"quantpad-data-python/{VERSION}"
 TICK_SCHEMAS = (
     "trades", "mbp-1", "mbp-10", "cmbp-1", "tcbbo", "cbbo-1s",

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/quantpad_data/memory.py

@@ -15,7 +15,7 @@ before fetching it, which is why it takes both.
 
 THE UNITS ARE NOT THE SAME, AND THAT IS THE WHOLE DIFFICULTY
 The service prices in DBN bytes: record count times record width, which is
-Databento's own billing arithmetic.  This process pays for the compressed wire
+upstream's own billing arithmetic.  This process pays for the compressed wire
 bytes, an Arrow table decoded from them, and a pandas frame copied out of that
 table -- partly all three at once.  Measured with
 scripts/measure_client_memory.py against production, peak RSS per priced byte

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/quantpad_data/v2.py

@@ -1,4 +1,4 @@
-"""Databento-shaped access to QuantPad's cache.
+"""Explicit-address access to QuantPad's cache.
 
 The v1 helpers take QuantPad's own arguments and infer the rest: which
 dataset a symbol lives in, what kind of symbol it is, how far back to
@@ -7,18 +7,7 @@ it is wrong it fails quietly — a specific futures contract returns an
 empty frame that looks exactly like a coverage gap.
 
 This module removes the inference.  Every call names its dataset and its
-symbology type, exactly as ``databento.Historical`` requires, and every
-response reports the address it actually used.  Code written against the
-Databento client transfers over with the client swapped:
-
-    import databento as db
-    client = db.Historical(key=...)
-    df = client.timeseries.get_range(
-        dataset="GLBX.MDP3", symbols="ESZ6", schema="ohlcv-1m",
-        start="2026-01-05", end="2026-01-06",
-    ).to_df()
-
-becomes
+symbology type, and every response reports the address it actually used:
 
     import quantpad_data as qpd
     client = qpd.v2.Historical()
@@ -27,9 +16,9 @@ becomes
         start="2026-01-05", end="2026-01-06",
     )
 
-The differences are deliberate and few: a DataFrame comes back directly
-rather than a DBNStore, and there is no cost or billing surface, because
-data is included in the QuantPad plan rather than metered per request.
+A DataFrame comes back directly, and there is no cost or billing surface,
+because data is included in the QuantPad plan rather than metered per
+request.
 """
 
 from __future__ import annotations
@@ -255,7 +244,7 @@ class _Namespace:
 
 
 class Timeseries(_Namespace):
-    """Mirrors ``databento.Historical.timeseries``."""
+    """Ranges of bars, ticks and book depth for an explicit address."""
 
     def get_range(
         self,
@@ -763,12 +752,12 @@ class Timeseries(_Namespace):
 
 
 class Symbology(_Namespace):
-    """Mirrors ``databento.Historical.symbology``, plus a way in.
+    """Symbol resolution, plus a way in.
 
     Every other call here demands an explicit ``dataset``, which is the
     point and also a dead end for someone holding the string "AAPL".
-    ``search`` is the one endpoint that answers that, and it has no
-    upstream counterpart because Databento assumes you already know.
+    ``search`` is the one endpoint that answers that; the rest of this
+    surface assumes you already know.
     """
 
     def search(
@@ -830,7 +819,7 @@ class Symbology(_Namespace):
 
 
 class Metadata(_Namespace):
-    """Mirrors ``databento.Historical.metadata``.
+    """Datasets, schemas, fields, coverage and request sizing.
 
     The cost and unit-price endpoints are deliberately absent: QuantPad
     data is included in the plan rather than metered, so a per-request
@@ -969,8 +958,8 @@ def _chain_frame(payload: dict) -> pd.DataFrame:
 class Options(_Namespace):
     """Options-chain enumeration.
 
-    Not part of Databento's client surface — upstream expects you to pull
-    the whole ``definition`` schema and filter it yourself.  This does
+    Not part of the usual historical-client surface, which expects you to
+    pull the whole ``definition`` schema and filter it yourself.  This does
     that server-side, because "download every instrument definition for
     the day" is a poor answer to "what strikes exist".
 
@@ -1008,7 +997,7 @@ class Options(_Namespace):
 
 
 class Batch(_Namespace):
-    """Mirrors ``databento.Historical.batch``, scoped to your own jobs.
+    """Batch extracts, scoped to your own jobs.
 
     Useful when a range is too large to stream in one sitting: submit,
     walk away, then hydrate the result into the cache so ordinary
@@ -1059,7 +1048,7 @@ class Batch(_Namespace):
 
 
 class Historical:
-    """A ``databento.Historical``-shaped view of QuantPad's cache.
+    """An explicit-address view of QuantPad's cache.
 
     Takes the same credentials as the v1 ``Client`` — an API key, or the
     injected token when running inside a QuantPad sandbox.

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/tests/test_packaging.py

@@ -21,6 +21,7 @@ from __future__ import annotations
 
 import ast
 import os
+import re
 import subprocess
 import sys
 import tarfile
@@ -53,6 +54,7 @@ def built(tmp_path_factory):
         # ./dist would make it skip in CI, where nothing has built there yet --
         # a test that skips exactly where it is needed.
         "wheel_path": wheel,
+        "sdist_path": sdist,
     }
 
 
@@ -182,3 +184,39 @@ class TestAFreshInstallExposesTheApi:
             f"a fresh install cannot answer for its own API:\n"
             f"{done.stdout}\n{done.stderr[-1500:]}"
         )
+
+
+class TestNothingShippedNamesTheDataVendor:
+    """QuantPad presents its market data as its own, and a published package is
+    as public as a response: PyPI serves every file in both artifacts, the
+    README is the project page, and ``help()`` in a user's sandbox prints the
+    docstrings. So nothing shipped may name the vendor -- read out of the
+    artifacts, for the same reason as everything else in this file."""
+
+    VENDOR = re.compile(r"data[\s_-]?bento", re.IGNORECASE)
+
+    @staticmethod
+    def _texts(built, kind):
+        if kind == "wheel":
+            with zipfile.ZipFile(built["wheel_path"]) as archive:
+                for name in archive.namelist():
+                    yield name, archive.read(name)
+        else:
+            with tarfile.open(built["sdist_path"]) as archive:
+                for member in archive.getmembers():
+                    if member.isfile():
+                        yield member.name, archive.extractfile(member).read()
+
+    @pytest.mark.parametrize("kind", ["wheel", "sdist"])
+    def test_no_shipped_file_names_the_vendor(self, built, kind):
+        offenders = [
+            name
+            for name, data in self._texts(built, kind)
+            if self.VENDOR.search(data.decode("utf-8", errors="replace"))
+        ]
+        assert not offenders, f"the {kind} names the data vendor in {offenders}"
+
+    def test_the_readme_is_in_what_was_checked(self, built):
+        """Guards the test above: the wheel's METADATA carries the README."""
+        names = [name for name, _ in self._texts(built, "wheel")]
+        assert any(name.endswith("METADATA") for name in names)

{quantpad_data-0.8.0 → quantpad_data-0.8.1}/tests/test_v2.py

@@ -1,4 +1,4 @@
-"""The Databento-shaped surface.
+"""The explicit-address surface.
 
 Two things are being checked. First that the wire calls carry exactly
 what the caller said and nothing the SDK invented — the whole reason
@@ -95,7 +95,7 @@ class TestNothingIsInferred:
         assert kwargs["json"]["symbols"] == ["ESZ6"]
 
     def test_a_single_symbol_string_is_sent_as_a_list(self):
-        """Databento accepts either; normalising here keeps the server
+        """Upstream accepts either; normalising here keeps the server
         contract one shape instead of two."""
         api, session = client_with([response(200, arrow_bytes(bars_table()))])
         api.timeseries.get_range(
@@ -104,7 +104,7 @@ class TestNothingIsInferred:
         )
         assert session.calls[0][2]["json"]["symbols"] == ["ESZ6"]
 
-    def test_the_default_stype_matches_databento_not_our_own_convention(self):
+    def test_the_default_stype_matches_upstream_not_our_own_convention(self):
         api, session = client_with([response(200, arrow_bytes(bars_table()))])
         api.timeseries.get_range(
             dataset="GLBX.MDP3", symbols="ESZ6", schema="ohlcv-1m",