marpledata 3.2.2__tar.gz → 3.2.3__tar.gz

{marpledata-3.2.2 → marpledata-3.2.3}/.gitignore

@@ -1,172 +1,172 @@
-lol.py
-.mdb_cache/
-matlab/bin/
-
-python/docs/_build/
-python/docs/api/marple.*.rst
-
-# Default ignored files
-/shelf/
-/workspace.xml
-
-# Byte-compiled / optimized / DLL files
-__pycache__/
-*.py[cod]
-*$py.class
-
-# C extensions
-*.so
-
-# Distribution / packaging
-.Python
-build/
-develop-eggs/
-dist/
-downloads/
-eggs/
-.eggs/
-lib/
-lib64/
-parts/
-sdist/
-var/
-wheels/
-share/python-wheels/
-*.egg-info/
-.installed.cfg
-*.egg
-MANIFEST
-
-# PyInstaller
-#  Usually these files are written by a python script from a template
-#  before PyInstaller builds the exe, so as to inject date/other infos into it.
-*.manifest
-*.spec
-
-# Installer logs
-pip-log.txt
-pip-delete-this-directory.txt
-
-# Unit test / coverage reports
-htmlcov/
-.tox/
-.nox/
-.coverage
-.coverage.*
-.cache
-nosetests.xml
-coverage.xml
-*.cover
-*.py,cover
-.hypothesis/
-.pytest_cache/
-cover/
-
-# Translations
-*.mo
-*.pot
-
-# Django stuff:
-*.log
-local_settings.py
-db.sqlite3
-db.sqlite3-journal
-
-# Flask stuff:
-instance/
-.webassets-cache
-
-# Scrapy stuff:
-.scrapy
-
-# Sphinx documentation
-docs/_build/
-
-# PyBuilder
-.pybuilder/
-target/
-
-# Jupyter Notebook
-.ipynb_checkpoints
-
-# IPython
-profile_default/
-ipython_config.py
-
-# pyenv
-#   For a library or package, you might want to ignore these files since the code is
-#   intended to run in multiple environments; otherwise, check them in:
-# .python-version
-
-# pipenv
-#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
-#   However, in case of collaboration, if having platform-specific dependencies or dependencies
-#   having no cross-platform support, pipenv may install dependencies that don't work, or not
-#   install all needed dependencies.
-#Pipfile.lock
-
-# poetry
-#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
-#poetry.lock
-
-# pdm
-#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
-#pdm.lock
-#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
-#   in version control.
-#   https://pdm.fming.dev/#use-with-ide
-.pdm.toml
-
-# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
-__pypackages__/
-
-# Celery stuff
-celerybeat-schedule
-celerybeat.pid
-
-# SageMath parsed files
-*.sage.py
-
-# Environments
-.env
-.venv
-env/
-venv/
-ENV/
-env.bak/
-venv.bak/
-
-# Spyder project settings
-.spyderproject
-.spyproject
-
-# Rope project settings
-.ropeproject
-
-# mkdocs documentation
-/site
-
-# mypy
-.mypy_cache/
-.dmypy.json
-dmypy.json
-
-# Pyre type checker
-.pyre/
-
-# pytype static type analyzer
-.pytype/
-
-# Cython debug symbols
-cython_debug/
-
-# PyCharm
-#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
-#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
-#  and can be added to the global gitignore or merged into this file.  For a more nuclear
-#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
-.idea/
-*.env
+lol.py
+.mdb_cache/
+matlab/bin/
+
+python/docs/_build/
+python/docs/api/marple.*.rst
+
+# Default ignored files
+/shelf/
+/workspace.xml
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/
+*.env

{marpledata-3.2.2 → marpledata-3.2.3}/.python-version

@@ -1 +1 @@
-3.11
+3.11

{marpledata-3.2.2 → marpledata-3.2.3}/AGENTS.md

@@ -1,29 +1,29 @@
-# Python SDK Guide
-
-This directory contains the Python SDK package published as `marpledata`.
-
-## Structure
-
-- `src/marple/`: package source.
-- `src/marple/db/`: Marple DB types and helpers.
-- `src/marple/insight.py`: Marple Insight client.
-- `tests/`: pytest integration tests.
-- `docs/`: Sphinx documentation.
-- `pyproject.toml`: package metadata, dependencies, and `uv` dependency groups.
-- `uv.lock`: locked Python dependencies.
-
-## Commands
-
-- Run tests with output: `uv run pytest -vs`
-- Build docs: `uv run --group docs sphinx-build -b html docs docs/_build/html`
-- Build package: `uv build`
-
-Run commands from `python/` unless a command explicitly says otherwise.
-
-## Conventions
-
-- Use `uv` for dependency, test, build, and docs workflows.
-- Keep Python SDK tests in `python/tests/`.
-- Integration tests run against live Marple services and may require
-  `MDB_TOKEN`, `MDB_URL`, `INSIGHT_TOKEN`, and `INSIGHT_URL`. Tests should skip
-  or fail clearly when required credentials are missing.
+# Python SDK Guide
+
+This directory contains the Python SDK package published as `marpledata`.
+
+## Structure
+
+- `src/marple/`: package source.
+- `src/marple/db/`: Marple DB types and helpers.
+- `src/marple/insight.py`: Marple Insight client.
+- `tests/`: pytest integration tests.
+- `docs/`: Sphinx documentation.
+- `pyproject.toml`: package metadata, dependencies, and `uv` dependency groups.
+- `uv.lock`: locked Python dependencies.
+
+## Commands
+
+- Run tests with output: `uv run pytest -vs`
+- Build docs: `uv run --group docs sphinx-build -b html docs docs/_build/html`
+- Build package: `uv build`
+
+Run commands from `python/` unless a command explicitly says otherwise.
+
+## Conventions
+
+- Use `uv` for dependency, test, build, and docs workflows.
+- Keep Python SDK tests in `python/tests/`.
+- Integration tests run against live Marple services and may require
+  `MDB_TOKEN`, `MDB_URL`, `INSIGHT_TOKEN`, and `INSIGHT_URL`. Tests should skip
+  or fail clearly when required credentials are missing.

{marpledata-3.2.2 → marpledata-3.2.3}/CHANGELOG.md

@@ -1,39 +1,45 @@
-# Changelog
-
-All notable changes to the Python SDK package `marpledata` will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [3.2.2] - 2026-06-01
-
-### Changed
-
-- Added default request timeouts and bounded retries to improve SDK reliability on spotty networks.
-- Retried idempotent direct-storage uploads while keeping Marple API POST retries conservative.
-
-## [3.2.1] - 2026-05-22
-
-### Changed
-
-- Included the SDK version in the `X-Request-Source` header sent by the Marple Insight client, matching the Marple DB client.
-
-## [3.2.0] - 2026-05-22
-
-### Added
-
-- Added the current Marple DB ingestion flow to `DataStream.push_file`.
-- Added automatic upload mode handling for server upload, Azure direct upload, single presigned upload, and multipart upload.
-- Added `concurrency` to control parallel direct-storage uploads.
-- Added `upload_mode="server"` to force uploads through the Marple DB API server when direct storage URLs are blocked.
-- Added `azure-storage-blob` as a runtime dependency for Azure-backed direct uploads.
-
-### Changed
-
-- Updated upload error handling to abort failed ingestions with a reason.
-- Undeprecated `DB.delete_stream` and `DB.delete_dataset` convenience methods.
-- Expanded README and Sphinx documentation for large-file uploads, forced server uploads, and integration test configuration.
-
-### Notes
-
-- `DB.push_file`, `DB.download_signal`, and `DB.update_metadata` remain deprecated compatibility paths. Prefer `DataStream`, `Dataset`, and `Signal` methods for new code.
+# Changelog
+
+All notable changes to the Python SDK package `marpledata` will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [3.2.3] - 2026-06-08
+
+### Changed
+
+- Bugfix build artifact `insight.py`
+
+## [3.2.2] - 2026-06-01
+
+### Changed
+
+- Added default request timeouts and bounded retries to improve SDK reliability on spotty networks.
+- Retried idempotent direct-storage uploads while keeping Marple API POST retries conservative.
+
+## [3.2.1] - 2026-05-22
+
+### Changed
+
+- Included the SDK version in the `X-Request-Source` header sent by the Marple Insight client, matching the Marple DB client.
+
+## [3.2.0] - 2026-05-22
+
+### Added
+
+- Added the current Marple DB ingestion flow to `DataStream.push_file`.
+- Added automatic upload mode handling for server upload, Azure direct upload, single presigned upload, and multipart upload.
+- Added `concurrency` to control parallel direct-storage uploads.
+- Added `upload_mode="server"` to force uploads through the Marple DB API server when direct storage URLs are blocked.
+- Added `azure-storage-blob` as a runtime dependency for Azure-backed direct uploads.
+
+### Changed
+
+- Updated upload error handling to abort failed ingestions with a reason.
+- Undeprecated `DB.delete_stream` and `DB.delete_dataset` convenience methods.
+- Expanded README and Sphinx documentation for large-file uploads, forced server uploads, and integration test configuration.
+
+### Notes
+
+- `DB.push_file`, `DB.download_signal`, and `DB.update_metadata` remain deprecated compatibility paths. Prefer `DataStream`, `Dataset`, and `Signal` methods for new code.

{marpledata-3.2.2 → marpledata-3.2.3}/CONTRIBUTING.md

@@ -1,76 +1,74 @@
-## Development (Python)
-
-### Testing
-
-The testing suite runs against a real linked DB & Insight deployment on our SaaS (e.g. Castro Comrades).
-Among other things it will create a stream, ingest a dataset, and export that dataset from Insight
-Upload tests also exercise server and multipart upload flows, and create/delete temporary streams with a test prefix.
-
-```bash
-export MDB_TOKEN=...
-export INSIGHT_TOKEN=...
-# Optional, defaults to SaaS URLs:
-export MDB_URL=https://db.marpledata.com/api/v1
-export INSIGHT_URL=https://insight.marpledata.com/api/v1
-uv run pytest -vs
-```
-
-### Documentation
-
-Build the Sphinx docs locally:
-
-```bash
-uv sync --group docs
-uv run sphinx-build -b html docs docs/_build/html
-```
-
-Open `docs/_build/html/index.html` in your browser to view the site.
-
-### Local build
-
-- `uv build`
-- `uv run pip install dist/*.whl` (Install in your local .venv)
-- `uv run python`
-  - `import marple`
-  - `marple.__version__`
-  - `from marple import Insight, DB`
-
-### Publishing (Test Pypi)
-
-Only once on your laptop
-
-- `uv build`
-- `uv publish --index testpypi`
-  - `username: __token__`
-  - `password: pypi-XXXXXXXXXXXXXXXXXXXXXXXXXXXX` (see 1Password)
-
-For every build
-
-- `uv version x.y.z.devi`
-- bump version in `__version__` variable
-- `uv build`
-- `uv publish --index testpypi`
-
-**Versioning**
-
-To ensure pip correctly updates our package, correct versioning is important. Use `major.minor.patch`
-
-- `major` when they make incompatible API changes
-- `minor` when they add functionality in a backwards-compatible manner
-- `patch` when they make backwards-compatible bug fixes
-
-**Recommended test workflow**
-
-- Publish to test Pypi
-- Open a docker container with the desired python version: `docker run -it python:3.11-alpine sh`
-- Install the test pypi package `pip install --upgrade -i --pre https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple marpledata`
-- If you want to publish again, change the version to one that has not been used before. Even if you delete a build via [the UI](https://test.pypi.org/manage/project/marpledata/releases/) you cannot publish that version again. For testing, you could use something like `x.y.z.dev1`, `x.y.z.dev2`, `x.y.z.dev3`, ...
-
-### Publishing (real Pypi)
-
-⚠ **Impacts users, be careful**
-
-- check version: `pyproject.toml:version`, `__init__.py:__version__`
-- `uv build`
-- `uv publish --token pypi-XXXXXXXXXXXXXXXXXXXXXXXXXXXX` (see 1Password)
-- Run the GitLab pipeline `pages` to build & release the docs
+## Development (Python)
+
+### Testing
+
+The testing suite runs against a real linked DB & Insight deployment on our SaaS (e.g. Castro Comrades).
+Among other things it will create a stream, ingest a dataset, and export that dataset from Insight
+Upload tests also exercise server and multipart upload flows, and create/delete temporary streams with a test prefix.
+
+```bash
+export MDB_TOKEN=...
+export INSIGHT_TOKEN=...
+# Optional, defaults to SaaS URLs:
+export MDB_URL=https://db.marpledata.com/api/v1
+export INSIGHT_URL=https://insight.marpledata.com/api/v1
+uv run pytest -vs
+```
+
+### Documentation
+
+Build the Sphinx docs locally:
+
+```bash
+uv sync --group docs
+uv run sphinx-build -b html docs docs/_build/html
+```
+
+Open `docs/_build/html/index.html` in your browser to view the site.
+
+### Local build
+
+- Bump version
+- Delete `./dist` folder
+- `uv build`
+- `uv run pip install dist/*.whl` (Install in your local .venv)
+- `uv run python`
+  - `import marple`
+  - `marple.__version__`
+  - `from marple import Insight, DB`
+
+### Publishing (Test Pypi)
+
+Only once on your laptop
+
+- `uv build`
+- `uv publish --index testpypi`
+  - `username: __token__`
+  - `password: pypi-XXXXXXXXXXXXXXXXXXXXXXXXXXXX` (see 1Password)
+
+For every build
+
+- `uv version x.y.z.devi`
+- bump version in `__version__` variable
+- `uv build`
+- `uv publish --index testpypi`
+
+**Versioning**
+
+To ensure pip correctly updates our package, correct versioning is important. Use `major.minor.patch`
+
+**Recommended test workflow**
+
+- Publish to test Pypi
+- Open a docker container with the desired python version: `docker run -it python:3.11-alpine sh`
+- Install the test pypi package `pip install --upgrade -i --pre https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple marpledata`
+- If you want to publish again, change the version to one that has not been used before. Even if you delete a build via [the UI](https://test.pypi.org/manage/project/marpledata/releases/) you cannot publish that version again. For testing, you could use something like `x.y.z.dev1`, `x.y.z.dev2`, `x.y.z.dev3`, ...
+
+### Publishing (real Pypi)
+
+⚠ **Impacts users, be careful**
+
+- check version: `pyproject.toml:version`, `__init__.py:__version__`
+- `uv build`
+- `uv publish --token pypi-XXXXXXXXXXXXXXXXXXXXXXXXXXXX` (see 1Password)
+- Run the GitLab pipeline `pages` to build & release the docs

{marpledata-3.2.2 → marpledata-3.2.3}/LICENSE

@@ -1,13 +1,13 @@
-Copyright 2022-2026 Marple BV
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
+Copyright 2022-2026 Marple BV
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.