mixinforge 0.238.0__tar.gz

mixinforge-0.238.0/.claude/settings.local.json

@@ -0,0 +1,18 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(wc:*)",
+      "Bash(python -m pytest --collect-only -q)",
+      "Bash(/usr/bin/python3 -m pytest:*)",
+      "Bash(find:*)",
+      "Bash(grep:*)",
+      "Bash(python3:*)",
+      "Bash(.venv/bin/python -m pytest:*)",
+      "Bash(python -m pytest:*)",
+      "Bash(pytest:*)",
+      "Bash(uv run pytest:*)",
+      "Bash(uv build:*)",
+      "Bash(tree:*)"
+    ]
+  }
+}

mixinforge-0.238.0/.github/workflows/ruff.yml

@@ -0,0 +1,27 @@
+name: Ruff
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    name: ruff check
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+
+      - name: Install Ruff
+        run: uv tool install ruff
+
+      - name: Run Ruff
+        run: ruff check .

mixinforge-0.238.0/.github/workflows/unit-tests.yml

@@ -0,0 +1,34 @@
+name: Run Pytest
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+
+    strategy:
+      matrix:
+        os: [ ubuntu-latest, windows-latest, macos-latest ]
+        python-version: [ "3.11", "3.12", "3.13", "3.14" ]
+
+    runs-on: ${{ matrix.os }}
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }} and uv
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install uv
+        run: pip install uv
+
+      - name: Install dependencies
+        run: uv pip install -e ".[dev]" --system
+
+      - name: Test with pytest
+        run: pytest

mixinforge-0.238.0/.gitignore

@@ -0,0 +1,158 @@
+
+# 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
+
+# uv
+uv.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__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/
+.DS_Store

mixinforge-0.238.0/.readthedocs.yaml

@@ -0,0 +1,33 @@
+# .readthedocs.yaml
+# Read the Docs configuration file
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+version: 2
+
+# Set the version of Python and other tools you might need
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.11"
+  jobs:
+    post_install:
+      - pip install -e .
+
+# Build documentation in the docs/ directory with Sphinx
+sphinx:
+  configuration: docs/source/conf.py
+  fail_on_warning: false
+
+# Specify the Python requirements required to build your documentation.
+python:
+  install:
+    - requirements: docs/requirements.txt
+    - method: pip
+      path: .
+      extra_requirements:
+        - docs
+
+# Output formats
+formats:
+  - pdf
+  - epub

mixinforge-0.238.0/CONTRIBUTING.md

@@ -0,0 +1,81 @@
+# Contributing to mixinforge
+
+Thank you for your interest in contributing to `mixinforge`! 
+Your help is greatly appreciated. These guidelines will help you get started.
+
+## Getting Started
+
+1.  **Fork and Clone:**
+    ```bash
+    git clone https://github.com/your-username/mixinforge.git
+    cd mixinforge
+    ```
+
+2.  **Install Dependencies:**
+    We use `uv` for package management.
+    ```bash
+    uv pip install -e ".[dev]"
+    ```
+
+3.  **Run Tests:**
+    Make sure the test suite passes before making changes.
+    ```bash
+    pytest
+    ```
+
+4.  **Run Linting:**
+    Make sure the code is free of linting errors.
+    ```bash
+    uv run ruff check .
+    ```
+
+## How to Contribute
+
+*   **Report Bugs:** Use the GitHub issue tracker to report bugs. 
+Please provide a clear description, steps to reproduce, and your Python version.
+*   **Suggest Enhancements:** Open an issue to discuss new features or improvements.
+
+### Submitting Pull Requests
+
+1.  **Create a Branch:**
+    ```bash
+    git checkout -b your-feature-name
+    ```
+2.  **Make Changes:** Write your code and add corresponding tests in the `tests/` directory.
+3.  **Follow Code Style:**
+    *   Adhere to PEP 8 guidelines.
+    *   Write clear, Google-style docstrings for public functions and classes. See [docstrings_comments.md](https://github.com/pythagoras-dev/mixinforge/blob/master/docstrings_comments.md) for detailed guidelines.
+    *   Add type hints where appropriate. See [type_hints.md](https://github.com/pythagoras-dev/mixinforge/blob/master/type_hints.md) for detailed guidelines.
+    *   For documentation build configuration, see [readthedocs.md](https://github.com/pythagoras-dev/mixinforge/blob/master/readthedocs.md).
+4. **Check Tests:** Make sure the test suite passes.
+5. **Check Linting:** Make sure the code is free of linting errors.
+6. **Write Commit Messages:** Follow the conventions below.
+7. **Push and Open a Pull Request:** Push your branch to your fork and open a pull request.
+
+### Commit Message Prefixes
+
+Use these prefixes for your commit messages:
+
+| Prefix  | Description                        |
+|:--------|:-----------------------------------|
+| `ENH:`  | Enhancement, new functionality     |
+| `BUG:`  | Bug fix                            |
+| `DOC:`  | Additions/updates to documentation |
+| `TST:`  | Additions/updates to tests         |
+| `BLD:`  | Build process/script updates       |
+| `PERF:` | Performance improvement            |
+| `REF:`  | Refactoring                        |
+| `TYP:`  | Type annotations                   |
+| `CLN:`  | Code cleanup                       |
+
+*Example: `ENH: Add support for nested parameter validation`*
+
+## License
+
+By contributing, you confirm that your contributions are an original work,
+or you have permission to use it, and agree that it will be 
+licensed under the MIT License.
+
+## Questions?
+
+Feel free to open an issue or contact the maintainer, Vlad (Volodymyr) Pavlov.

mixinforge-0.238.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024-2026  Vlad (Volodymyr) Pavlov.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.