vbase 1.0.0__tar.gz → 2.0.0__tar.gz

vbase-2.0.0/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog
+
+All notable changes are documented here, following
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+Versions follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+Earlier releases were not tracked in this file; see the
+[commit history](https://github.com/validityBase/vbase-py/commits/main/)
+for prior changes.
+
+## [Unreleased]
+
+## [2.0.0] - 2026-10-28
+
+### Changed
+
+- Require Python 3.11 or later. Drop support for Python 3.8 through 3.10 (#84).
+- Accept Web3 versions greater than or equal to 7.15 and less than 9 (#106).
+- Set upper bounds for runtime dependencies (#63, #106).
+- Remove the unused `imageio` runtime dependency (#110).
+
+### Fixed
+
+- Use a matching `AddSet` receipt event to confirm a new set commitment.
+  Check the event's user and set CID. This avoids a false `add_set` failure
+  when an RPC backend returns stale state (#86).
+- Retry the state check if a successful `add_set` transaction has no `AddSet`
+  receipt event. Fail if the set commitment cannot be confirmed after the
+  configured retries. Commitment confirmation does not guarantee immediate
+  visibility through an indexing service (#86).

{vbase-1.0.0 → vbase-2.0.0}/MANIFEST.in

@@ -1,3 +1,4 @@
 include README.md
 include requirements.in
 recursive-include vbase/core/abi *.json
+include CHANGELOG.md

{vbase-1.0.0/vbase.egg-info → vbase-2.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vbase
-Version: 1.0.0
+Version: 2.0.0
 Summary: vBase Python Software Development Kit (SDK)
 Author-email: vBase <tech@vbase.com>
 License-Expression: Apache-2.0
@@ -10,32 +10,31 @@ Project-URL: Issues, https://github.com/validityBase/vbase-py/issues
 Keywords: vbase,blockchain,provenance,web3,sdk
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
-Requires-Python: >=3.8
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
 License-File: NOTICE.txt
-Requires-Dist: hexbytes>=0.3.1
-Requires-Dist: numpy>=1.24.0
-Requires-Dist: pandas>=2.0.0
-Requires-Dist: python-dotenv>=1.0.0
-Requires-Dist: requests>=2.31.0
-Requires-Dist: web3==7.15.0
-Requires-Dist: sqlmodel>=0.0.24
-Requires-Dist: imageio
-Requires-Dist: retry>=0.9.2
+Requires-Dist: hexbytes<3,>=1.2.0
+Requires-Dist: numpy<3,>=1.24.0
+Requires-Dist: pandas<4,>=2.0.0
+Requires-Dist: python-dotenv<2,>=1.0.0
+Requires-Dist: requests<3,>=2.31.0
+Requires-Dist: web3<9,>=7.15.0
+Requires-Dist: sqlmodel<0.1,>=0.0.24
+Requires-Dist: retry<1,>=0.9.2
 Dynamic: license-file
 
 # vbase-py
 
 vBase Python Software Development Kit (SDK)
 
-- Python 3.8+ support
+- Python 3.11+ support
 
 ---
 
 ## License
 
-This project is licensed under the Apache 2.0 License - see the [LICENSE.txt](LICENSE.txt) file for details.
+This project is licensed under the Apache 2.0 License - see the [LICENSE.txt](https://github.com/validityBase/vbase-py/blob/main/LICENSE.txt) file for details.
 
 ## Introduction
 
@@ -62,18 +61,17 @@ Install the package from PyPI:
 pip install vbase
 ```
 
-See the [local installation](https://docs.vbase.com/getting-started/python-quickstart/local-installation) and the [cloud notebooks](https://docs.vbase.com/getting-started/python-quickstart/cloud-notebooks) guides to get started using vBase from Python.
+See the [local installation](https://docs.vbase.com/python-sdk/python-quickstart-readme/quickstart-1) and the [cloud notebooks](https://docs.vbase.com/python-sdk/python-quickstart-readme/quickstart) guides to get started using vBase from Python.
 
 ## Development
 
-Development and CI installs use generated requirements locks with pip
-hash-checking mode:
+Install the generated development lock and package locally:
 
 ```bash
-python -m pip install --require-hashes -r requirements-dev.txt
+python -m pip install --require-hashes -r requirements/dev.txt
 python -m pip install --no-deps --no-build-isolation -e .
 ```
 
-To update dependencies, edit the relevant `.in` file and regenerate the lock
-file with `pip-compile --generate-hashes`. See
-[internal/specs/python-dependency-hashes.md](internal/specs/python-dependency-hashes.md).
+See `internal/specs/python-dependency-hashes.md` in this repository for the
+dependency layout, lock policy, package metadata rules, and regeneration
+commands.

{vbase-1.0.0 → vbase-2.0.0}/README.md

@@ -2,13 +2,13 @@
 
 vBase Python Software Development Kit (SDK)
 
-- Python 3.8+ support
+- Python 3.11+ support
 
 ---
 
 ## License
 
-This project is licensed under the Apache 2.0 License - see the [LICENSE.txt](LICENSE.txt) file for details.
+This project is licensed under the Apache 2.0 License - see the [LICENSE.txt](https://github.com/validityBase/vbase-py/blob/main/LICENSE.txt) file for details.
 
 ## Introduction
 
@@ -35,18 +35,17 @@ Install the package from PyPI:
 pip install vbase
 ```
 
-See the [local installation](https://docs.vbase.com/getting-started/python-quickstart/local-installation) and the [cloud notebooks](https://docs.vbase.com/getting-started/python-quickstart/cloud-notebooks) guides to get started using vBase from Python.
+See the [local installation](https://docs.vbase.com/python-sdk/python-quickstart-readme/quickstart-1) and the [cloud notebooks](https://docs.vbase.com/python-sdk/python-quickstart-readme/quickstart) guides to get started using vBase from Python.
 
 ## Development
 
-Development and CI installs use generated requirements locks with pip
-hash-checking mode:
+Install the generated development lock and package locally:
 
 ```bash
-python -m pip install --require-hashes -r requirements-dev.txt
+python -m pip install --require-hashes -r requirements/dev.txt
 python -m pip install --no-deps --no-build-isolation -e .
 ```
 
-To update dependencies, edit the relevant `.in` file and regenerate the lock
-file with `pip-compile --generate-hashes`. See
-[internal/specs/python-dependency-hashes.md](internal/specs/python-dependency-hashes.md).
+See `internal/specs/python-dependency-hashes.md` in this repository for the
+dependency layout, lock policy, package metadata rules, and regeneration
+commands.

{vbase-1.0.0 → vbase-2.0.0}/pyproject.toml

@@ -7,7 +7,7 @@ name = "vbase"
 dynamic = ["version", "dependencies"]
 description = "vBase Python Software Development Kit (SDK)"
 readme = "README.md"
-requires-python = ">=3.8"
+requires-python = ">=3.11"
 license = "Apache-2.0"
 authors = [
 	{ name = "vBase", email = "tech@vbase.com" },

vbase-2.0.0/requirements.in

@@ -0,0 +1,8 @@
+hexbytes>=1.2.0,<3
+numpy>=1.24.0,<3
+pandas>=2.0.0,<4
+python-dotenv>=1.0.0,<2
+requests>=2.31.0,<3
+web3>=7.15.0,<9
+sqlmodel>=0.0.24,<0.1
+retry>=0.9.2,<1

{vbase-1.0.0 → vbase-2.0.0}/setup.py

@@ -2,5 +2,4 @@
 
 from setuptools import setup
 
-
 setup()

{vbase-1.0.0 → vbase-2.0.0}/vbase/__init__.py

@@ -3,7 +3,6 @@
 A Python library for interacting with the validityBase (vBase) platform
 """
 
-from vbase._version import __version__
 from vbase.core.aggregate_indexing_service import AggregateIndexingService
 from vbase.core.failover_indexing_service import FailoverIndexingService
 from vbase.core.forwarder_commitment_service import ForwarderCommitmentService
@@ -41,6 +40,7 @@ from vbase.core.vbase_object import (
 from vbase.core.web3_http_commitment_service import Web3HTTPCommitmentService
 from vbase.core.web3_http_commitment_service_test import Web3HTTPCommitmentServiceTest
 from vbase.utils.log import get_default_logger
+from ._version import __version__
 
 __all__ = [
     "__version__",
@@ -53,7 +53,6 @@ __all__ = [
     "IndexingService",
     "Web3HTTPIndexingService",
     "SQLIndexingService",
-
     "ChainSetMatchingService",
     "HeadBasedSetMatchingService",
     "FuzzySetMatchingService",
@@ -61,7 +60,6 @@ __all__ = [
     "SetMatch",
     "SetMatchingCriteria",
     "TimestampedCid",
-
     "FailoverIndexingService",
     "AggregateIndexingService",
     "VBaseObject",

{vbase-1.0.0 → vbase-2.0.0}/vbase/_version.py

@@ -1,3 +1,3 @@
 """Package version."""
 
-__version__ = "1.0.0"
+__version__ = "2.0.0"

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/aggregate_indexing_service.py

@@ -10,7 +10,7 @@ _LOG = get_default_logger(__name__)
 _LOG.setLevel(logging.INFO)
 
 
-class AggregateIndexingService(IndexingService):
+class AggregateIndexingService(IndexingService):  # pylint: disable=abstract-method
     """This indexing service aggregates the responses from a set of indexing services
 
     Each operation executes a corresponding method on all services and aggregates the results.

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/commitment_service.py

@@ -84,8 +84,21 @@ class CommitmentService(ABC):
         It does not specify how a hash is built and does not provide
         a schema for hashing complex information.
 
+        The operation is idempotent. A successful transaction receipt containing
+        a matching ``AddSet`` event is authoritative for the submitted write and
+        avoids a potentially stale state read. If an idempotent transaction emits
+        no event, the service confirms the existing commitment using bounded,
+        exponential-backoff retries.
+
+        Transaction confirmation does not guarantee immediate visibility through
+        an indexing service. Consumers that query indexing immediately after a
+        write may need read-your-write handling based on the returned transaction
+        hash.
+
         :param set_cid: The CID identifying the set.
         :return: The commitment log containing commitment receipt info.
+        :raises RuntimeError: If a matching event is absent and the commitment
+            cannot be confirmed after retrying.
         """
 
     @abstractmethod

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/failover_indexing_service.py

@@ -9,7 +9,7 @@ _LOG = get_default_logger(__name__)
 _LOG.setLevel(logging.INFO)
 
 
-class FailoverIndexingService(IndexingService):
+class FailoverIndexingService(IndexingService):  # pylint: disable=abstract-method
     """This indexing service calls a set of indexing services one after another
     and provides a failover mechanism to ensure that if one service fails,
     another service can be used to retrieve the data.

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/set_matching/__init__.py

@@ -3,10 +3,8 @@
 Core classes for set matching services in the validityBase (vBase) platform Python library
 """
 
-from vbase.core.set_matching.chain_set_matching_service import (
-    ChainSetMatchingService,
-)
 from vbase.core.set_matching.base_set_matching_service import BaseSetMatchingService
+from vbase.core.set_matching.chain_set_matching_service import ChainSetMatchingService
 from vbase.core.set_matching.fuzzy_set_matching_service import FuzzySetMatchingService
 from vbase.core.set_matching.head_based_set_matching_service import (
     HeadBasedSetMatchingService,

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/set_matching/base_set_matching_service.py

@@ -11,7 +11,7 @@ from vbase.core.models import EventAddSetObject, LastBatchProcessingTime
 from vbase.core.set_matching.types import SetIdentifier, SetMatch, SetMatchingCriteria
 
 
-class BaseSetMatchingService(ABC):
+class BaseSetMatchingService(ABC):  # pylint: disable=too-few-public-methods
     """
     Abstract base class for set matching strategies.
 

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/set_matching/chain_set_matching_service.py

@@ -2,12 +2,13 @@
 Aggregate set matching strategies.
 """
 
-
 from vbase.core.set_matching.base_set_matching_service import BaseSetMatchingService
 from vbase.core.set_matching.types import SetMatch, SetMatchingCriteria
 
 
-class ChainSetMatchingService(BaseSetMatchingService):
+class ChainSetMatchingService(
+    BaseSetMatchingService
+):  # pylint: disable=too-few-public-methods
     """
     Aggregate multiple set matching strategies to return first non-empty result.
 

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/set_matching/fuzzy_set_matching_service.py

@@ -18,7 +18,9 @@ from vbase.core.set_matching.types import (
 )
 
 
-class FuzzySetMatchingService(BaseSetMatchingService):
+class FuzzySetMatchingService(
+    BaseSetMatchingService
+):  # pylint: disable=too-few-public-methods
     """
     Service for performing fuzzy set matching with tolerance.
     Finds sets whose elements match the criteria within a configurable tolerance.
@@ -142,7 +144,9 @@ class FuzzySetMatchingService(BaseSetMatchingService):
                 rank=s.rank,
                 set_cid=s.key.set_cid,
                 user=s.key.user,
-                last_matching_element_timestamp=s.objects[s.projected_last_element_index].timestamp,
+                last_matching_element_timestamp=s.objects[
+                    s.projected_last_element_index
+                ].timestamp,
                 data_freshness_timestamp=last_batch,
                 is_full_match=(
                     s.set_length == len(sorted_criteria.objects)
@@ -292,8 +296,8 @@ class FuzzySetMatchingService(BaseSetMatchingService):
                     dp[i][j] = dp[i - 1][j - 1]
                 else:
                     dp[i][j] = 1 + min(
-                        dp[i - 1][j],      # deletion
-                        dp[i][j - 1],      # insertion
+                        dp[i - 1][j],  # deletion
+                        dp[i][j - 1],  # insertion
                         dp[i - 1][j - 1],  # substitution
                     )
 
@@ -325,9 +329,7 @@ class FuzzySetMatchingService(BaseSetMatchingService):
         if not criteria.objects:
             return []
 
-        required_matches = max(
-            1, math.ceil(len(criteria.objects) * (1.0 - tolerance))
-        )
+        required_matches = max(1, math.ceil(len(criteria.objects) * (1.0 - tolerance)))
 
         # Collect all criteria CIDs
         criteria_cids = [obj.object_cid for obj in criteria.objects]

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/set_matching/head_based_set_matching_service.py

@@ -6,10 +6,17 @@ from sqlmodel import Session, create_engine, select
 
 from vbase.core.models import EventAddSetObject
 from vbase.core.set_matching.base_set_matching_service import BaseSetMatchingService
-from vbase.core.set_matching.types import ObjectSetData, SetIdentifier, SetMatch, SetMatchingCriteria
+from vbase.core.set_matching.types import (
+    ObjectSetData,
+    SetIdentifier,
+    SetMatch,
+    SetMatchingCriteria,
+)
 
 
-class HeadBasedSetMatchingService(BaseSetMatchingService):
+class HeadBasedSetMatchingService(
+    BaseSetMatchingService
+):  # pylint: disable=too-few-public-methods
     """
     Service for performing head-based set matching.
     Finds sets whose head (first elements) matches the elements specified in the criteria.
@@ -25,10 +32,7 @@ class HeadBasedSetMatchingService(BaseSetMatchingService):
     (distributed sets).
     """
 
-    def __init__(
-        self,
-        db_url: str
-    ):
+    def __init__(self, db_url: str):
         self.db_url = db_url
         self.db_engine = create_engine(db_url)
 
@@ -68,7 +72,6 @@ class HeadBasedSetMatchingService(BaseSetMatchingService):
                 return []
             event_rows = self._load_candidate_events(session, candidate_keys)
 
-
         # Build ObjectSetData from event_rows (already ordered by timestamp)
         candidate_sets_dict: dict[SetIdentifier, ObjectSetData] = {}
         for event_row in event_rows:

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/set_matching/types.py

@@ -5,6 +5,8 @@ Core types for indexing and matching strategies.
 from dataclasses import dataclass, field
 
 from vbase.core.models import EventAddSetObject
+
+
 @dataclass
 class TimestampedCid:
     """Pair of object_cid and its timestamp criteria."""
@@ -23,6 +25,7 @@ class SetMatchingCriteria:
 
     objects: list[TimestampedCid]
 
+
 @dataclass(frozen=True)
 class SetMatch:
     """
@@ -48,6 +51,7 @@ class SetIdentifier:
     Unique identifier for a set, based on its set_cid and user.
     Sets can span multiple chains (distributed sets).
     """
+
     set_cid: str
     user: str
 

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/sql_indexing_service.py

@@ -19,7 +19,7 @@ from .models import (
 INDEXING_STALE_THRESHOLD_SECONDS = 60
 
 
-class SQLIndexingService(IndexingService):
+class SQLIndexingService(IndexingService):  # pylint: disable=abstract-method
     """
     Indexing service based on chain indexing data from sql db.
     """

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/vbase_client.py

@@ -106,8 +106,21 @@ class VBaseClient:
         It does not specify how a hash is built and does not provide
         a schema for hashing complex information.
 
+        The operation is idempotent. A successful transaction receipt containing
+        a matching ``AddSet`` event is authoritative for the submitted write and
+        avoids a potentially stale state read. If an idempotent transaction emits
+        no event, the service confirms the existing commitment using bounded,
+        exponential-backoff retries.
+
+        Transaction confirmation does not guarantee immediate visibility through
+        an indexing service. Consumers that query indexing immediately after a
+        write may need read-your-write handling based on the returned transaction
+        hash.
+
         :param set_cid: The CID (hash) identifying the set.
         :return: The commitment log containing commitment receipt info.
+        :raises RuntimeError: If a matching event is absent and the commitment
+            cannot be confirmed after retrying.
         """
         return self.commitment_service.add_set(set_cid)
 

{vbase-1.0.0 → vbase-2.0.0}/vbase/core/web3_commitment_service.py

@@ -14,6 +14,7 @@ from io import TextIOWrapper
 from typing import List, Optional, Type, Union
 
 import pandas as pd
+from retry.api import retry_call
 from web3 import Web3
 from web3.contract import Contract
 from web3.contract.base_contract import EventLogErrorFlags
@@ -32,6 +33,10 @@ class Web3CommitmentService(CommitmentService, ABC):
     either directly or via a forwarder.
     """
 
+    RETRY_TRIES = 3
+    RETRY_DELAY = 1
+    RETRY_BACKOFF = 2
+
     def __init__(
         self, w3: Web3, commitment_service_contract: Union[Type[Contract], Contract]
     ):
@@ -113,6 +118,24 @@ class Web3CommitmentService(CommitmentService, ABC):
             _LOG.error(msg)
             raise RuntimeError(msg)
 
+    def _require_user_set_exists(self, user: str, set_cid: str) -> None:
+        """Raise if a set commitment is not visible for a user."""
+        if not self.user_set_exists(user, set_cid):
+            raise RuntimeError(
+                "AddSet event not found and set commitment does not exist"
+            )
+
+    def _user_set_exists_with_retry(self, user: str, set_cid: str) -> None:
+        """Confirm set visibility with bounded exponential-backoff retries."""
+        retry_call(
+            self._require_user_set_exists,
+            fargs=[user, set_cid],
+            tries=self.RETRY_TRIES,
+            delay=self.RETRY_DELAY,
+            backoff=self.RETRY_BACKOFF,
+            logger=_LOG,
+        )
+
     def _add_set_worker(self, set_cid: str, receipt: TxReceipt) -> dict:
         """Process results of a addSect transaction.
 
@@ -132,6 +155,12 @@ class Web3CommitmentService(CommitmentService, ABC):
             cl = dict(add_set_events[0]["args"])
             # Convert bytestrings to strings to allow serialization for upper layers.
             cl["setCid"] = bytes_to_hex_str(cl["setCid"])
+            if str(cl["user"]).lower() != self.get_default_user().lower():
+                raise RuntimeError("AddSet event user does not match requested user")
+            if cl["setCid"].lower() != set_cid.lower():
+                raise RuntimeError(
+                    "AddSet event set CID does not match requested set CID"
+                )
             cl["transactionHash"] = receipt["transactionHash"]
             # Expose committer as userAddress for API consumers.
             self._init_receipt_fields(cl)
@@ -147,14 +176,10 @@ class Web3CommitmentService(CommitmentService, ABC):
         else:
             # No event means addSet was a no-op (set already existed).
             cl = {}
-
-        # Confirm that the set exists following the completed commitment.
-        # This is useful for catching any transaction failures
-        # or errors in the node infrastructure to report failures properly.
-        # Note that this may be a forwarded transaction.
-        # In this case, the receipt["from"] is the forwarder/relayer address
-        # and cl["user"] is the user address for the commitment.
-        assert self.user_set_exists(self.get_default_user(), set_cid)
+            # Confirm that an eventless transaction was the expected idempotent no-op.
+            # A matching AddSet event is already authoritative proof of a new
+            # commitment and avoids a stale read from a different RPC backend.
+            self._user_set_exists_with_retry(self.get_default_user(), set_cid)
 
         _LOG.debug("Commitment log:\n%s", pprint.pformat(cl))
         return cl

{vbase-1.0.0 → vbase-2.0.0/vbase.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vbase
-Version: 1.0.0
+Version: 2.0.0
 Summary: vBase Python Software Development Kit (SDK)
 Author-email: vBase <tech@vbase.com>
 License-Expression: Apache-2.0
@@ -10,32 +10,31 @@ Project-URL: Issues, https://github.com/validityBase/vbase-py/issues
 Keywords: vbase,blockchain,provenance,web3,sdk
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
-Requires-Python: >=3.8
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
 License-File: NOTICE.txt
-Requires-Dist: hexbytes>=0.3.1
-Requires-Dist: numpy>=1.24.0
-Requires-Dist: pandas>=2.0.0
-Requires-Dist: python-dotenv>=1.0.0
-Requires-Dist: requests>=2.31.0
-Requires-Dist: web3==7.15.0
-Requires-Dist: sqlmodel>=0.0.24
-Requires-Dist: imageio
-Requires-Dist: retry>=0.9.2
+Requires-Dist: hexbytes<3,>=1.2.0
+Requires-Dist: numpy<3,>=1.24.0
+Requires-Dist: pandas<4,>=2.0.0
+Requires-Dist: python-dotenv<2,>=1.0.0
+Requires-Dist: requests<3,>=2.31.0
+Requires-Dist: web3<9,>=7.15.0
+Requires-Dist: sqlmodel<0.1,>=0.0.24
+Requires-Dist: retry<1,>=0.9.2
 Dynamic: license-file
 
 # vbase-py
 
 vBase Python Software Development Kit (SDK)
 
-- Python 3.8+ support
+- Python 3.11+ support
 
 ---
 
 ## License
 
-This project is licensed under the Apache 2.0 License - see the [LICENSE.txt](LICENSE.txt) file for details.
+This project is licensed under the Apache 2.0 License - see the [LICENSE.txt](https://github.com/validityBase/vbase-py/blob/main/LICENSE.txt) file for details.
 
 ## Introduction
 
@@ -62,18 +61,17 @@ Install the package from PyPI:
 pip install vbase
 ```
 
-See the [local installation](https://docs.vbase.com/getting-started/python-quickstart/local-installation) and the [cloud notebooks](https://docs.vbase.com/getting-started/python-quickstart/cloud-notebooks) guides to get started using vBase from Python.
+See the [local installation](https://docs.vbase.com/python-sdk/python-quickstart-readme/quickstart-1) and the [cloud notebooks](https://docs.vbase.com/python-sdk/python-quickstart-readme/quickstart) guides to get started using vBase from Python.
 
 ## Development
 
-Development and CI installs use generated requirements locks with pip
-hash-checking mode:
+Install the generated development lock and package locally:
 
 ```bash
-python -m pip install --require-hashes -r requirements-dev.txt
+python -m pip install --require-hashes -r requirements/dev.txt
 python -m pip install --no-deps --no-build-isolation -e .
 ```
 
-To update dependencies, edit the relevant `.in` file and regenerate the lock
-file with `pip-compile --generate-hashes`. See
-[internal/specs/python-dependency-hashes.md](internal/specs/python-dependency-hashes.md).
+See `internal/specs/python-dependency-hashes.md` in this repository for the
+dependency layout, lock policy, package metadata rules, and regeneration
+commands.

{vbase-1.0.0 → vbase-2.0.0}/vbase.egg-info/SOURCES.txt

@@ -1,3 +1,4 @@
+CHANGELOG.md
 LICENSE.txt
 MANIFEST.in
 NOTICE.txt

vbase-2.0.0/vbase.egg-info/requires.txt

@@ -0,0 +1,8 @@
+hexbytes<3,>=1.2.0
+numpy<3,>=1.24.0
+pandas<4,>=2.0.0
+python-dotenv<2,>=1.0.0
+requests<3,>=2.31.0
+web3<9,>=7.15.0
+sqlmodel<0.1,>=0.0.24
+retry<1,>=0.9.2

vbase-1.0.0/requirements.in

@@ -1,9 +0,0 @@
-hexbytes>=0.3.1
-numpy>=1.24.0
-pandas>=2.0.0
-python-dotenv>=1.0.0
-requests>=2.31.0
-web3==7.15.0
-sqlmodel>=0.0.24
-imageio
-retry>=0.9.2

vbase-1.0.0/vbase.egg-info/requires.txt

@@ -1,9 +0,0 @@
-hexbytes>=0.3.1
-numpy>=1.24.0
-pandas>=2.0.0
-python-dotenv>=1.0.0
-requests>=2.31.0
-web3==7.15.0
-sqlmodel>=0.0.24
-imageio
-retry>=0.9.2