matrx-utils 2.0.2__tar.gz → 2.0.3__tar.gz

{matrx_utils-2.0.2 → matrx_utils-2.0.3}/CLAUDE.md

@@ -25,7 +25,7 @@ If you catch yourself writing `from matrx_connect import …` at the top of a fi
 - **Data handling** (`matrx_utils.data_handling`): `DataTransformer`, validators, URL tools.
 - **File handling** (`matrx_files`): `FileManager`, `FileHandler`, `BatchHandler`, `open_any_file`.
 - **Image variant presets** (`matrx_files`): `PODCAST_VARIANTS`, `SOCIAL_VARIANTS`, `WEB_VARIANTS`, `EMAIL_VARIANTS`, `LOGO_VARIANTS`, `AVATAR_VARIANTS`, `FAVICON_VARIANTS`, `SOCIAL_BASELINE`, plus the `PRESETS` registry and the composer helpers `compose_preset(name, include_baseline, extra_variants)`, `get_preset(name)`, `list_preset_names()`. Hosts consume these to render the same variant set everywhere — every public asset gets the social baseline (og + thumbnail + tiny) appended automatically unless explicitly disabled.
-- **Cloud storage** (`matrx_files.cloud_sync`): `S3Backend`, `SupabaseBackend`, `ServerBackend`, `CloudSyncConfig`, `SyncEngine`, permissions + versioning.
+- **Cloud storage** (`matrx_files.cloud_sync`): `S3Backend`, `ServerBackend`, `CloudSyncConfig`, `SyncEngine`, permissions + versioning.
 - **Centralized URL minting** — `SyncEngine.build_urls_for_record(_async)` is the **single source of truth** for the `{url, cdn_url, signed_url, download_url}` contract a file response carries. `managed_write_async` and `replace_file_async` populate the same shape on every `SyncResult`. Callers MUST consume `result.url` / `result.cdn_url` directly and never re-mint via `_router.get_url_async(...)`. The backends accept `response_content_disposition` and `response_content_type` kwargs so attachment-URLs flow through to S3 unchanged.
 - **Field / schema processing** (`matrx_utils.field_processing`): `camel_to_snake`, `process_field_definitions`, `generate_complete_code`.
 - **Code analysis tools** (`matrx_utils.code_context`, `matrx_utils.package_analysis`, `matrx_utils.react_analysis`): developer utilities for scanning codebases.
@@ -58,7 +58,7 @@ Inside this package:
 
 - **Never** read `os.environ["…"]` directly outside `conf.py`. Route through `settings`, which already falls back to env vars.
 - **Never** reach into a specific host's context shape. The `UserContext` protocol defines what we need; if you need more, extend the protocol and provide defaults.
-- The `CloudSyncConfig` / `SupabaseBackend` / `S3Backend` classes must accept explicit credentials in their constructors and only fall back to `settings` if the caller didn't pass them in. See `file_handling/cloud_sync/` for the pattern.
+- The `CloudSyncConfig` / `S3Backend` classes must accept explicit credentials in their constructors and only fall back to `settings` if the caller didn't pass them in. See `file_handling/cloud_sync/` for the pattern.
 
 ---
 

{matrx_utils-2.0.2 → matrx_utils-2.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: matrx-utils
-Version: 2.0.2
+Version: 2.0.3
 Summary: Core shared utilities for the Matrx ecosystem (file handling now lives in matrx-files)
 Project-URL: Homepage, https://github.com/AI-Matrix-Engine/aidream-current
 Project-URL: Repository, https://github.com/AI-Matrix-Engine/aidream-current
@@ -28,7 +28,7 @@ Description-Content-Type: text/markdown
 
 # matrx-utils
 
-Foundation utilities for the Matrx ecosystem — cloud file handling (AWS S3, Supabase Storage, local/server filesystems), a pluggable settings + request-context layer, and a set of developer helpers (fancy printing, data transforms, field-processing, code analysis).
+Foundation utilities for the Matrx ecosystem — cloud file handling (AWS S3 and local/server filesystems), a pluggable settings + request-context layer, and a set of developer helpers (fancy printing, data transforms, field-processing, code analysis).
 
 `matrx-utils` is the bottom of the Matrx dependency graph. It has **no sibling dependencies**. Everything else (`matrx-connect`, `matrx-orm`, `matrx-graph`, `matrx-scraper`, `matrx-ai`) depends on it, directly or transitively.
 
@@ -49,7 +49,7 @@ Python 3.13+ required.
 | `matrx_utils.fancy_prints` | `vcprint`, `vclist`, `print_link`, `MatrixPrintLog`, `to_matrx_json` |
 | `matrx_utils.data_handling` | `DataTransformer`, URL and value validators |
 | `matrx_files` | `FileManager`, `FileHandler`, `BatchHandler`, `open_any_file` |
-| `matrx_files.cloud_sync` | `S3Backend`, `SupabaseBackend`, `ServerBackend`, `CloudSyncConfig`, `SyncEngine` + permissions and versioning |
+| `matrx_files.cloud_sync` | `S3Backend`, `ServerBackend`, `CloudSyncConfig`, `SyncEngine` + permissions and versioning |
 | `matrx_utils.field_processing` | `camel_to_snake`, `process_field_definitions`, `generate_complete_code` |
 | `matrx_utils.code_context`, `matrx_utils.package_analysis`, `matrx_utils.react_analysis` | Developer utilities for scanning codebases |
 
@@ -59,11 +59,11 @@ Out of the box, `matrx-utils` reads its configuration from environment variables
 
 ```python
 from matrx_utils import vcprint, settings
-from matrx_files.cloud_sync import SupabaseBackend
+from matrx_files.cloud_sync import S3Backend
 
 vcprint("hello")
 vcprint(settings.SUPABASE_URL)           # read from env
-backend = SupabaseBackend()              # credentials resolved from settings
+backend = S3Backend()                    # credentials resolved from settings
 backend.write("reports/today.json", b"{}")
 ```
 

{matrx_utils-2.0.2 → matrx_utils-2.0.3}/README.md

@@ -1,6 +1,6 @@
 # matrx-utils
 
-Foundation utilities for the Matrx ecosystem — cloud file handling (AWS S3, Supabase Storage, local/server filesystems), a pluggable settings + request-context layer, and a set of developer helpers (fancy printing, data transforms, field-processing, code analysis).
+Foundation utilities for the Matrx ecosystem — cloud file handling (AWS S3 and local/server filesystems), a pluggable settings + request-context layer, and a set of developer helpers (fancy printing, data transforms, field-processing, code analysis).
 
 `matrx-utils` is the bottom of the Matrx dependency graph. It has **no sibling dependencies**. Everything else (`matrx-connect`, `matrx-orm`, `matrx-graph`, `matrx-scraper`, `matrx-ai`) depends on it, directly or transitively.
 
@@ -21,7 +21,7 @@ Python 3.13+ required.
 | `matrx_utils.fancy_prints` | `vcprint`, `vclist`, `print_link`, `MatrixPrintLog`, `to_matrx_json` |
 | `matrx_utils.data_handling` | `DataTransformer`, URL and value validators |
 | `matrx_files` | `FileManager`, `FileHandler`, `BatchHandler`, `open_any_file` |
-| `matrx_files.cloud_sync` | `S3Backend`, `SupabaseBackend`, `ServerBackend`, `CloudSyncConfig`, `SyncEngine` + permissions and versioning |
+| `matrx_files.cloud_sync` | `S3Backend`, `ServerBackend`, `CloudSyncConfig`, `SyncEngine` + permissions and versioning |
 | `matrx_utils.field_processing` | `camel_to_snake`, `process_field_definitions`, `generate_complete_code` |
 | `matrx_utils.code_context`, `matrx_utils.package_analysis`, `matrx_utils.react_analysis` | Developer utilities for scanning codebases |
 
@@ -31,11 +31,11 @@ Out of the box, `matrx-utils` reads its configuration from environment variables
 
 ```python
 from matrx_utils import vcprint, settings
-from matrx_files.cloud_sync import SupabaseBackend
+from matrx_files.cloud_sync import S3Backend
 
 vcprint("hello")
 vcprint(settings.SUPABASE_URL)           # read from env
-backend = SupabaseBackend()              # credentials resolved from settings
+backend = S3Backend()                    # credentials resolved from settings
 backend.write("reports/today.json", b"{}")
 ```
 

{matrx_utils-2.0.2 → matrx_utils-2.0.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "matrx-utils"
-version = "2.0.2"
+version = "2.0.3"
 description = "Core shared utilities for the Matrx ecosystem (file handling now lives in matrx-files)"
 readme = "README.md"
 license = { text = "MIT" }