muscles-data-sqlalchemy 0.1.1__tar.gz → 0.2.0__tar.gz

{muscles_data_sqlalchemy-0.1.1 → muscles_data_sqlalchemy-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: muscles-data-sqlalchemy
-Version: 0.1.1
+Version: 0.2.0
 Summary: SQLAlchemy SqlResourcePort adapter for muscles-data
 Author-email: "Denis B." <denis@butko.info>
 Project-URL: Homepage, https://github.com/butkoden/muscles-data-sqlalchemy
@@ -31,7 +31,7 @@ owns typed ports, resource runtime and diagnostics, while this package owns the
 SQLAlchemy-backed `SqlResourcePort` adapter.
 
 Use this package when a project wants direct SQLAlchemy sessions through the
-same data resource runtime without wiring `muscles-sql` first.
+same data resource runtime without wiring `muscles-data-sql` first.
 
 ## Related packages
 
@@ -54,19 +54,21 @@ same data resource runtime without wiring `muscles-sql` first.
 
 ## Usage
 
-Register the factory in the project composition root:
+Register this adapter once in the application composition root when building
+the shared `DataAdapterCatalog`, alongside other configured adapters:
 
 ```python
-from muscles_data.catalog import DataAdapterCatalog
-from muscles_data.ports import SqlResourcePort
-from muscles_data.runtime import DataRuntime
-from muscles_data_sqlalchemy import SqlAlchemySqlResourceFactory
-
-catalog = DataAdapterCatalog.with_defaults()
 catalog.register(SqlAlchemySqlResourceFactory())
+```
+
+The `sql.local` resource itself is declared in the application's central
+`data.resources` configuration shown below. A package resolves the port from
+the existing runtime; it does not build another catalog or `DataRuntime`:
+
+```python
+from muscles.data.ports import SqlResourcePort
 
-runtime = DataRuntime(config=config, catalog=catalog)
-sql = runtime.require_port("sql.local", SqlResourcePort)
+sql = app.resource.connect("sql.local", SqlResourcePort)
 ```
 
 Resource config stays in the project:

{muscles_data_sqlalchemy-0.1.1 → muscles_data_sqlalchemy-0.2.0}/README.md

@@ -7,7 +7,7 @@ owns typed ports, resource runtime and diagnostics, while this package owns the
 SQLAlchemy-backed `SqlResourcePort` adapter.
 
 Use this package when a project wants direct SQLAlchemy sessions through the
-same data resource runtime without wiring `muscles-sql` first.
+same data resource runtime without wiring `muscles-data-sql` first.
 
 ## Related packages
 
@@ -30,19 +30,21 @@ same data resource runtime without wiring `muscles-sql` first.
 
 ## Usage
 
-Register the factory in the project composition root:
+Register this adapter once in the application composition root when building
+the shared `DataAdapterCatalog`, alongside other configured adapters:
 
 ```python
-from muscles_data.catalog import DataAdapterCatalog
-from muscles_data.ports import SqlResourcePort
-from muscles_data.runtime import DataRuntime
-from muscles_data_sqlalchemy import SqlAlchemySqlResourceFactory
-
-catalog = DataAdapterCatalog.with_defaults()
 catalog.register(SqlAlchemySqlResourceFactory())
+```
+
+The `sql.local` resource itself is declared in the application's central
+`data.resources` configuration shown below. A package resolves the port from
+the existing runtime; it does not build another catalog or `DataRuntime`:
+
+```python
+from muscles.data.ports import SqlResourcePort
 
-runtime = DataRuntime(config=config, catalog=catalog)
-sql = runtime.require_port("sql.local", SqlResourcePort)
+sql = app.resource.connect("sql.local", SqlResourcePort)
 ```
 
 Resource config stays in the project:

{muscles_data_sqlalchemy-0.1.1 → muscles_data_sqlalchemy-0.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "muscles-data-sqlalchemy"
-version = "0.1.1"
+version = "0.2.0"
 description = "SQLAlchemy SqlResourcePort adapter for muscles-data"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -44,3 +44,4 @@ package-dir = {"" = "src"}
 
 [tool.setuptools.packages.find]
 where = ["src"]
+include = ["muscles.data.sqlalchemy*"]

{muscles_data_sqlalchemy-0.1.1/src/muscles_data_sqlalchemy → muscles_data_sqlalchemy-0.2.0/src/muscles/data/sqlalchemy}/adapter.py

@@ -6,9 +6,9 @@ from collections.abc import Callable
 from dataclasses import asdict
 from typing import Any, Mapping
 
-from muscles_data.config import DataResourceConfig
-from muscles_data.errors import DataError
-from muscles_data.models import DataCapability, HealthResult, InspectResult
+from muscles.data.config import DataResourceConfig
+from muscles.data.errors import DataError
+from muscles.data.models import DataCapability, HealthResult, InspectResult
 
 
 _ENGINE_UNSET = object()

{muscles_data_sqlalchemy-0.1.1 → muscles_data_sqlalchemy-0.2.0}/src/muscles_data_sqlalchemy.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: muscles-data-sqlalchemy
-Version: 0.1.1
+Version: 0.2.0
 Summary: SQLAlchemy SqlResourcePort adapter for muscles-data
 Author-email: "Denis B." <denis@butko.info>
 Project-URL: Homepage, https://github.com/butkoden/muscles-data-sqlalchemy
@@ -31,7 +31,7 @@ owns typed ports, resource runtime and diagnostics, while this package owns the
 SQLAlchemy-backed `SqlResourcePort` adapter.
 
 Use this package when a project wants direct SQLAlchemy sessions through the
-same data resource runtime without wiring `muscles-sql` first.
+same data resource runtime without wiring `muscles-data-sql` first.
 
 ## Related packages
 
@@ -54,19 +54,21 @@ same data resource runtime without wiring `muscles-sql` first.
 
 ## Usage
 
-Register the factory in the project composition root:
+Register this adapter once in the application composition root when building
+the shared `DataAdapterCatalog`, alongside other configured adapters:
 
 ```python
-from muscles_data.catalog import DataAdapterCatalog
-from muscles_data.ports import SqlResourcePort
-from muscles_data.runtime import DataRuntime
-from muscles_data_sqlalchemy import SqlAlchemySqlResourceFactory
-
-catalog = DataAdapterCatalog.with_defaults()
 catalog.register(SqlAlchemySqlResourceFactory())
+```
+
+The `sql.local` resource itself is declared in the application's central
+`data.resources` configuration shown below. A package resolves the port from
+the existing runtime; it does not build another catalog or `DataRuntime`:
+
+```python
+from muscles.data.ports import SqlResourcePort
 
-runtime = DataRuntime(config=config, catalog=catalog)
-sql = runtime.require_port("sql.local", SqlResourcePort)
+sql = app.resource.connect("sql.local", SqlResourcePort)
 ```
 
 Resource config stays in the project:

{muscles_data_sqlalchemy-0.1.1 → muscles_data_sqlalchemy-0.2.0}/src/muscles_data_sqlalchemy.egg-info/SOURCES.txt

@@ -1,7 +1,7 @@
 README.md
 pyproject.toml
-src/muscles_data_sqlalchemy/__init__.py
-src/muscles_data_sqlalchemy/adapter.py
+src/muscles/data/sqlalchemy/__init__.py
+src/muscles/data/sqlalchemy/adapter.py
 src/muscles_data_sqlalchemy.egg-info/PKG-INFO
 src/muscles_data_sqlalchemy.egg-info/SOURCES.txt
 src/muscles_data_sqlalchemy.egg-info/dependency_links.txt

muscles_data_sqlalchemy-0.2.0/src/muscles_data_sqlalchemy.egg-info/top_level.txt

@@ -0,0 +1 @@
+muscles

{muscles_data_sqlalchemy-0.1.1 → muscles_data_sqlalchemy-0.2.0}/tests/test_integration.py

@@ -5,12 +5,12 @@ from pathlib import Path
 from tempfile import TemporaryDirectory
 
 import pytest
-from muscles_data.catalog import DataAdapterCatalog
-from muscles_data.config import DataConfig
-from muscles_data.ports import SqlResourcePort
-from muscles_data.runtime import DataRuntime
+from muscles.data.catalog import DataAdapterCatalog
+from muscles.data.config import DataConfig
+from muscles.data.ports import SqlResourcePort
+from muscles.data.runtime import DataRuntime
 
-from muscles_data_sqlalchemy import SqlAlchemySqlResourceFactory
+from muscles.data.sqlalchemy import SqlAlchemySqlResourceFactory
 
 
 pytestmark = [
@@ -50,7 +50,7 @@ def test_sqlalchemy_real_session_and_health_lifecycle():
                 assert session.execute(text("select 1")).scalar_one() == 1
             assert sql.doctor()["status"] == "ok"
             assert runtime.doctor()["status"] == "ok"
-            contracts = pytest.importorskip("muscles_data.contracts")
+            contracts = pytest.importorskip("muscles.data.contracts")
             contract = getattr(contracts, "assert_sql_resource_contract", None)
             if contract is not None:
                 contract(lambda: sql)

{muscles_data_sqlalchemy-0.1.1 → muscles_data_sqlalchemy-0.2.0}/tests/test_sqlalchemy_adapter.py

@@ -1,13 +1,13 @@
 from __future__ import annotations
 
 import pytest
-from muscles_data.catalog import DataAdapterCatalog
-from muscles_data.config import DataConfig
-from muscles_data.models import DataCapability
-from muscles_data.ports import SqlResourcePort
-from muscles_data.runtime import DataRuntime
+from muscles.data.catalog import DataAdapterCatalog
+from muscles.data.config import DataConfig
+from muscles.data.models import DataCapability
+from muscles.data.ports import SqlResourcePort
+from muscles.data.runtime import DataRuntime
 
-from muscles_data_sqlalchemy import (
+from muscles.data.sqlalchemy import (
     SqlAlchemyClientMissingError,
     SqlAlchemyConnectionError,
     SqlAlchemySqlResourceFactory,

muscles_data_sqlalchemy-0.1.1/src/muscles_data_sqlalchemy.egg-info/top_level.txt

@@ -1 +0,0 @@
-muscles_data_sqlalchemy