maya-brew 0.0.4__tar.gz

maya_brew-0.0.4/.github/pull_request_template.md

@@ -0,0 +1,24 @@
+# Pull Request
+
+## What does this PR do?
+
+Briefly describe your changes.
+
+## Related Issue
+
+Link to issue (if any):
+
+mortenbohne/maya-brew#XX
+
+## Testing
+
+How did you test your changes? (Leave blank if not needed)
+
+## Checklist
+
+- [ ] I reviewed my code
+- [ ] My change does not break existing features
+
+## Extra notes
+
+(Optional)

maya_brew-0.0.4/.github/workflows/docker-publish.yml

@@ -0,0 +1,44 @@
+name: Build & Publish Docker (GHCR)
+
+on:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  packages: write
+
+jobs:
+  docker:
+    runs-on: ubuntu-latest
+    env:
+      IMAGE: ghcr.io/${{ github.repository_owner }}/maya-brew
+    steps:
+      - name: Checkout
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8
+        with:
+          persist-credentials: false
+          fetch-depth: 1
+
+      - name: Login to GHCR
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u "${{ github.repository_owner }}" --password-stdin
+
+      - name: Build & Push
+        run: |
+          set -euo pipefail
+          SHORT_SHA="${GITHUB_SHA::7}"
+          docker buildx build \
+            -t "${IMAGE}:latest" \
+            -t "${IMAGE}:sha-${SHORT_SHA}" \
+            --push \
+            .
+          echo "SHORT_SHA=${SHORT_SHA}" >> "$GITHUB_ENV"
+
+      - name: Summary
+        run: |
+          set -euo pipefail
+          SHORT_SHA="${SHORT_SHA:-${GITHUB_SHA::7}}"
+          {
+            echo "Published tags:"
+            echo "${IMAGE}:latest"
+            echo "${IMAGE}:sha-${SHORT_SHA}"
+          } | tee -a "$GITHUB_STEP_SUMMARY"

maya_brew-0.0.4/.github/workflows/linter.yml

@@ -0,0 +1,110 @@
+---
+# This GitHub Actions workflow is triggered by pull requests, pushes to the
+# develop branch, and manual dispatch events. It sets up a Python environment,
+# installs project dependencies, and then runs Super-Linter on the codebase.
+# The workflow can auto-fix issues on push (committing directly) and produce
+# a PR commit with fixes (via git-auto-commit-action) when running in PRs.
+
+name: Lint Code Base
+
+on:
+  workflow_dispatch:
+  pull_request:
+  push:
+    branches:
+      - develop
+
+permissions:
+  contents: write
+  statuses: write
+
+jobs:
+  build:
+    name: Lint Code Base
+    runs-on: ubuntu-latest
+    steps:
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - name: Checkout Code
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+      - name: Cache Python dependencies
+        uses: actions/cache@v4
+        with:
+          path: |
+            .venv
+            uv.lock
+          key: ${{ runner.os }}-uv-${{ hashFiles('pyproject.toml', 'uv.lock') }}
+          restore-keys: |
+            ${{ runner.os }}-uv-
+      - name: Install uv
+        run: pip install uv
+      - name: Sync dependencies
+        run: uv sync --extra dev
+      - name: Prepare credentials for auto-fix (push only)
+        if: github.event_name == 'push'
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git remote set-url origin "https://x-access-token:${GITHUB_TOKEN}@github.com/${{ github.repository }}"
+      - name: Lint Code Base
+        uses: super-linter/super-linter/slim@7bba2eeb89d01dc9bfd93c497477a57e72c83240
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          DEFAULT_BRANCH: develop
+          APPLY_FIXES: true
+          APPLY_FIXES_EVENT: push
+          APPLY_FIXES_MODE: commit
+          VALIDATE_ALL_CODEBASE: true
+          LINTER_RULES_PATH: /
+          PYTHON_PYLINT_CONFIG_FILE: ./pyproject.toml
+          PYTHONPATH: "${{ github.workspace }}/.venv/lib/python3.11/site-packages:${{ github.workspace }}/src"
+          SAVE_SUPER_LINTER_SUMMARY: true
+          ENABLE_GITHUB_ACTIONS_STEP_SUMMARY: true
+          VALIDATE_CHECKOV: true
+          VALIDATE_GITLEAKS: true
+          VALIDATE_GITHUB_ACTIONS_ZIZMOR: true
+          VALIDATE_JSON: true
+          VALIDATE_JSON_PRETTIER: true
+          VALIDATE_MARKDOWN: true
+          VALIDATE_MARKDOWN_PRETTIER: true
+          VALIDATE_NATURAL_LANGUAGE: true
+          VALIDATE_PYTHON_BLACK: true
+          VALIDATE_PYTHON_ISORT: true
+          VALIDATE_PYTHON_RUFF: true
+          VALIDATE_YAML_PRETTIER: true
+          FIX_GITHUB_ACTIONS_ZIZMOR: true
+          FIX_JSON_PRETTIER: true
+          FIX_JSON: true
+          FIX_MARKDOWN_PRETTIER: true
+          FIX_MARKDOWN: true
+          FIX_NATURAL_LANGUAGE: true
+          FIX_PYTHON_BLACK: true
+          FIX_PYTHON_ISORT: true
+          FIX_PYTHON_RUFF: true
+          FIX_YAML_PRETTIER: true
+      - name: Prepare credentials for PR auto-fix commit
+        if: >
+          github.event_name == 'pull_request' &&
+          github.event.pull_request.head.repo.full_name == github.repository
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          git remote set-url origin "https://x-access-token:${GITHUB_TOKEN}@github.com/${{ github.repository }}"
+      - name: Commit and push linting fixes
+        if: >
+          github.event_name == 'pull_request' &&
+          github.ref_name != github.event.repository.default_branch &&
+          github.event.pull_request.head.repo.full_name == github.repository
+        uses: stefanzweifel/git-auto-commit-action@778341af668090896ca464160c2def5d1d1a3eb0
+        with:
+          branch: ${{ github.event.pull_request.head.ref }}
+          commit_message: "chore: fix linting issues"
+          commit_user_name: super-linter
+          commit_user_email: super-linter@super-linter.dev

maya_brew-0.0.4/.github/workflows/release.yml

@@ -0,0 +1,46 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install build dependencies (uv)
+        run: |
+          pip install uv
+
+      - name: Build distribution (wheel + sdist) with uv (dynamic version from latest tag)
+        run: |
+          uv build
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist-artifacts
+          path: dist/*
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@ab69e431e9c9f48a3310be0a56527c679f56e04d
+        with:
+          packages-dir: dist
+          skip-existing: true

maya_brew-0.0.4/.github/workflows/test-mayapy.yml

@@ -0,0 +1,44 @@
+name: Pytest Maya 2026
+
+on:
+  workflow_dispatch:
+  pull_request:
+  push:
+    branches:
+      - develop
+
+permissions:
+  contents: read
+  packages: read
+
+jobs:
+  mayapy-tests:
+    runs-on: ubuntu-latest
+    container:
+      image: ghcr.io/${{ github.repository_owner }}/maya-brew:sha-9daa1a4
+      options: --user root
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v5
+        with:
+          persist-credentials: false
+          fetch-depth: 1
+      - name: Install uv
+        run: mayapy -m pip install uv
+      - name: Cache Python dependencies
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/.cache/pip
+            ~/.cache/uv
+          key: mayapy-${{ runner.os }}-${{ hashFiles('pyproject.toml') }}
+          restore-keys: |
+            mayapy-${{ runner.os }}-
+      - name: Install project (runtime + dev extras) with uv
+        run: |
+          mayapy -m uv pip install ".[dev]"
+      - name: Run pytest
+        run: mayapy -m pytest tests/ -q
+      - name: Summary
+        if: success()
+        run: echo "mayapy pytest run succeeded." >> "$GITHUB_STEP_SUMMARY"

maya_brew-0.0.4/.gitignore

@@ -0,0 +1,179 @@
+# 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
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.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/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# 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/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+.idea/*
+
+# Super-Linter generated GitHub config snapshot (do not commit)
+github_conf/

maya_brew-0.0.4/.mise.toml

@@ -0,0 +1,11 @@
+[tasks."docker:build"]
+description = "Build Docker image"
+run = "docker build -t maya-brew ."
+
+[tasks."docker:run"]
+description = "Run Docker container"
+run = "docker run -it --rm maya-brew"
+
+[tasks."docker:maya"]
+description = "Run Maya in Docker container"
+run = "mise run docker:run mayapy"

maya_brew-0.0.4/Dockerfile

@@ -0,0 +1,49 @@
+FROM rockylinux:9.3
+
+ENV PYTHONDONTWRITEBYTECODE=1 \
+    MAYA_LOCATION=/usr/autodesk/maya2026 \
+    PATH=/usr/autodesk/maya2026/bin:$PATH
+
+# hadolint ignore=DL3041
+RUN set -eux; \
+    dnf install -y epel-release && \
+    dnf install -y --allowerasing \
+        curl \
+        libX11 libXext libXt libXi libXtst libXmu libXpm \
+        libXft libXcursor libXinerama libXcomposite libXdamage libXrender libXrandr \
+        mesa-libGL mesa-libGLU libglvnd-opengl libglvnd-egl \
+        libSM libICE freetype fontconfig \
+        libxkbcommon libxkbfile \
+        libtiff \
+        libva libvdpau \
+        nss nspr \
+        alsa-lib && \
+    dnf clean all && rm -rf /var/cache/dnf
+
+# Download & install Maya
+RUN set -eux; \
+    curl -L -o /maya.tgz "https://efulfillment.autodesk.com/NetSWDLD/prd/2026/MAYA/901073B8-F0A1-3952-A459-9CA36A875C41/Autodesk_Maya_2026_2_Update_Linux_64bit.tgz" && \
+    mkdir /maya_install && \
+    tar -xf /maya.tgz -C /maya_install && \
+    rpm --force -ivh /maya_install/Packages/Maya2026_64-*.x86_64.rpm && \
+    rm -rf /maya.tgz /maya_install && \
+    rm -rf /usr/autodesk/maya2026/Examples \
+           /usr/autodesk/maya2026/brushImages \
+           /usr/autodesk/maya2026/icons \
+           /usr/autodesk/maya2026/include \
+           /usr/autodesk/maya2026/presets \
+           /usr/autodesk/maya2026/qml \
+           /usr/autodesk/maya2026/synColor \
+           /usr/autodesk/maya2026/translations
+
+# Add healthcheck script and non-root user
+# hadolint ignore=SC2016
+RUN set -eux; \
+    printf '#!/usr/bin/env bash\nset -e\n[ -x "$MAYA_LOCATION/bin/maya" ] || exit 1\nexit 0\n' >/usr/local/bin/healthcheck && \
+    chmod +x /usr/local/bin/healthcheck && \
+    groupadd -r maya && useradd -r -g maya -d /home/maya -m maya
+
+HEALTHCHECK --interval=30m --timeout=30s --start-period=30s --retries=3 CMD ["/usr/local/bin/healthcheck"]
+
+WORKDIR /home/maya
+USER maya

maya_brew-0.0.4/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Morten Bøhne
+
+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.

maya_brew-0.0.4/PKG-INFO

@@ -0,0 +1,71 @@
+Metadata-Version: 2.4
+Name: maya-brew
+Version: 0.0.4
+Summary: Safe interaction with python in maya
+Project-URL: Homepage, https://github.com/mortenbohne/maya-brew
+Project-URL: Repository, https://github.com/mortenbohne/maya-brew
+Project-URL: Documentation, https://github.com/mortenbohne/maya-brew#readme
+Project-URL: Issues, https://github.com/mortenbohne/maya-brew/issues
+Project-URL: Changelog, https://github.com/mortenbohne/maya-brew/releases
+Author-email: Morten Bøhne <github@mortenbohne.dk>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: 3d,autodesk,maya,pipeline
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Multimedia :: Graphics :: 3D Modeling
+Requires-Python: >=3.11
+Requires-Dist: colorama
+Requires-Dist: structlog
+Provides-Extra: dev
+Requires-Dist: maya-stubs; extra == 'dev'
+Requires-Dist: pytest; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# maya-brew
+
+> **Status: Pre-Alpha** – Interfaces are experimental and may change without notice. Pin exact versions if using in
+> automation.
+
+What you need after a long day of wrestling with Maya Python.
+
+[![Super-Linter](https://github.com/mortenbohne/maya-brew/actions/workflows/linter.yml/badge.svg)](https://github.com/marketplace/actions/super-linter)
+
+---
+
+## Overview
+
+`maya-brew` aims to provide safer, more structured interaction patterns when scripting or tooling inside Autodesk Maya.
+
+Goals:
+
+- Reduce foot‑guns when using Python inside Maya
+- Offer utilities that behave well with Maya’s quirks
+
+## Background
+
+`maya-brew` draws inspiration from some of the ergonomic goals that motivated
+[PyMEL](https://github.com/LumaPictures/pymel): making Maya’s Python interface feel more “Pythonic,” safer, and more
+discoverable. PyMEL historically provided rich object wrappers around nodes, attributes, and other scene elements;
+for many workflows this improved readability and reduced boilerplate.
+
+However, over time several practical factors led to the decision to start a lightweight alternative instead of
+extending PyMEL itself:
+
+- Scope & Complexity: PyMEL’s dynamic wrapping and layered abstractions can introduce startup overhead, indirection, and
+  occasional debugging friction.
+- Historical Churn: A long evolution, multiple contributors, and some legacy design choices make selective modernization
+  non‑trivial.
+- Maintenance & Momentum: While still usable, PyMEL no longer appears to have the same pace of active development or
+  broad community push it once did.
+- Adoption Fit: Many pipelines only need a thin set of safety/ergonomic helpers—not a full object layer over
+  `maya.cmds`.
+
+### Acknowledgment
+
+PyMEL significantly influenced how many technical artists approach Maya scripting, and this project stands on that
+conceptual foundation. `maya-brew` simply narrows the focus: take the useful ergonomic ideas, shed the heavy wrapping,
+and keep to the canonical APIs.

maya_brew-0.0.4/README.md

@@ -0,0 +1,44 @@
+# maya-brew
+
+> **Status: Pre-Alpha** – Interfaces are experimental and may change without notice. Pin exact versions if using in
+> automation.
+
+What you need after a long day of wrestling with Maya Python.
+
+[![Super-Linter](https://github.com/mortenbohne/maya-brew/actions/workflows/linter.yml/badge.svg)](https://github.com/marketplace/actions/super-linter)
+
+---
+
+## Overview
+
+`maya-brew` aims to provide safer, more structured interaction patterns when scripting or tooling inside Autodesk Maya.
+
+Goals:
+
+- Reduce foot‑guns when using Python inside Maya
+- Offer utilities that behave well with Maya’s quirks
+
+## Background
+
+`maya-brew` draws inspiration from some of the ergonomic goals that motivated
+[PyMEL](https://github.com/LumaPictures/pymel): making Maya’s Python interface feel more “Pythonic,” safer, and more
+discoverable. PyMEL historically provided rich object wrappers around nodes, attributes, and other scene elements;
+for many workflows this improved readability and reduced boilerplate.
+
+However, over time several practical factors led to the decision to start a lightweight alternative instead of
+extending PyMEL itself:
+
+- Scope & Complexity: PyMEL’s dynamic wrapping and layered abstractions can introduce startup overhead, indirection, and
+  occasional debugging friction.
+- Historical Churn: A long evolution, multiple contributors, and some legacy design choices make selective modernization
+  non‑trivial.
+- Maintenance & Momentum: While still usable, PyMEL no longer appears to have the same pace of active development or
+  broad community push it once did.
+- Adoption Fit: Many pipelines only need a thin set of safety/ergonomic helpers—not a full object layer over
+  `maya.cmds`.
+
+### Acknowledgment
+
+PyMEL significantly influenced how many technical artists approach Maya scripting, and this project stands on that
+conceptual foundation. `maya-brew` simply narrows the focus: take the useful ergonomic ideas, shed the heavy wrapping,
+and keep to the canonical APIs.