anpyra 0.1.0__tar.gz

anpyra-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,33 @@
+---
+name: Bug report
+about: Report a failure in documented Anpyra behavior
+title: "[Bug] "
+---
+
+# 🐛 Bug Report
+
+## 🎯 Expected and actual behavior
+
+Describe what should happen and what happened.
+
+## 🔁 Minimal reproduction
+
+Provide the exact command, smallest app source, relevant `anpyra.toml` and complete error. State whether the syntax is documented as supported.
+
+## 🧰 Environment
+
+- OS and Python version:
+- Anpyra version/commit and cryptography version:
+- Installation method (editable/wheel):
+- Device model/API, if relevant:
+- Install/launch result, if relevant:
+
+## 🔎 Evidence
+
+Attach a relevant IR/Dalvik excerpt, redacted build report or focused runtime log if useful. Do not include private keys or unrelated device/app data.
+
+## ✅ Checks tried
+
+- [ ] Consulted troubleshooting and the supported language reference.
+- [ ] Reproduced with a minimal source/project.
+- [ ] Stated which host/device checks passed or remain pending.

anpyra-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature proposal
+about: Propose an app capability and its compiler/runtime contract
+title: "[Feature] "
+---
+
+# 🧩 Feature Proposal
+
+## 🎯 Concrete use case
+
+What application behavior do you need? What currently blocks it?
+
+## ✍️ Proposed source/API
+
+Show a minimal proposed form and label it as future syntax.
+
+## ⚙️ Semantics and implementation impact
+
+Describe types, evaluation/lifecycle behavior, and likely front-end/IR/DEX/UI/package changes. Identify a roadmap phase/dependency.
+
+## 🧪 Acceptance criteria
+
+What source errors, binary checks and device behavior would prove completion?
+
+## 📋 Alternatives and scope
+
+List a narrower implementation if useful and clarify what remains out of scope.

anpyra-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,23 @@
+# 📝 Change Description
+
+## 🎯 Problem and resulting behavior
+
+Describe the concrete failure/use case and what now happens.
+
+## 🧱 Affected stages
+
+List source/API/config/compiler/backend/package/docs areas changed and any compatibility impact.
+
+## 🧪 Validation
+
+Record actual commands/results. Distinguish checks run locally from CI/device checks still pending.
+
+## 📚 Documentation and roadmap
+
+- [ ] Relevant user/developer examples and references match behavior.
+- [ ] Roadmap/changelog status reflects implemented work and evidence.
+- [ ] No private keys, generated APKs, environments or caches are included.
+
+## 🚧 Remaining limits
+
+Describe unresolved behavior, untested platforms or deliberate limitations.

anpyra-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,112 @@
+name: Publish Python package
+run-name: Publish ${{ inputs.tag }} to ${{ inputs.repository }}
+
+on:
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: Existing version tag, for example v0.1.0
+        type: string
+        required: true
+      repository:
+        description: Package index
+        type: choice
+        options:
+          - testpypi
+          - pypi
+        default: testpypi
+        required: true
+
+permissions:
+  contents: read
+
+concurrency:
+  group: publish-${{ inputs.repository }}-${{ inputs.tag }}
+  cancel-in-progress: false
+
+jobs:
+  validate:
+    if: github.ref == 'refs/heads/main'
+    uses: ./.github/workflows/tests.yml
+    with:
+      ref: refs/tags/${{ inputs.tag }}
+
+  build:
+    needs: validate
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - name: Check out the release tag
+        uses: actions/checkout@v4
+        with:
+          ref: refs/tags/${{ inputs.tag }}
+          persist-credentials: false
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          version: '0.12.21'
+          enable-cache: false
+
+      - name: Check version and tag
+        env:
+          RELEASE_TAG: ${{ inputs.tag }}
+        run: python scripts/check_release.py --tag "$RELEASE_TAG"
+
+      - name: Build wheel and source distribution
+        run: uv build --no-create-gitignore --out-dir dist
+
+      - name: Check archive contents and metadata
+        run: |
+          python scripts/check_release.py --dist dist
+          uvx --from twine twine check --strict dist/*
+
+      - name: Install the wheel and build a new Android app
+        run: |
+          uv venv --python 3.12 /tmp/anpyra-release-smoke
+          uv pip install --python /tmp/anpyra-release-smoke/bin/python dist/*.whl
+          cd /tmp
+          /tmp/anpyra-release-smoke/bin/anpyra --version
+          /tmp/anpyra-release-smoke/bin/anpyra init release-app --package dev.anpyra.release
+          /tmp/anpyra-release-smoke/bin/anpyra build release-app
+          /tmp/anpyra-release-smoke/bin/anpyra verify release-app/build/dev.anpyra.release.apk
+
+      - name: Save checked distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-distributions
+          path: |
+            dist/*.whl
+            dist/*.tar.gz
+          if-no-files-found: error
+          retention-days: 14
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    environment:
+      name: ${{ inputs.repository }}
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - name: Download checked distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: python-distributions
+          path: dist
+
+      - name: Publish to TestPyPI
+        if: inputs.repository == 'testpypi'
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+      - name: Publish to PyPI
+        if: inputs.repository == 'pypi'
+        uses: pypa/gh-action-pypi-publish@release/v1

anpyra-0.1.0/.github/workflows/tests.yml

@@ -0,0 +1,36 @@
+name: Tests
+on:
+  push:
+  pull_request:
+  workflow_call:
+    inputs:
+      ref:
+        description: Git reference to validate for a release
+        type: string
+        required: false
+        default: ''
+permissions:
+  contents: read
+jobs:
+  test:
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+        python: ['3.11', '3.13']
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ inputs.ref || github.ref }}
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+      - run: python -m pip install -e ".[dev]"
+      - run: ruff check src tests examples scripts
+      - run: ruff format --check src tests examples scripts
+      - run: python scripts/check_docs.py
+      - run: python -m unittest discover -s tests -v
+      - run: anpyra build examples/hello
+      - run: anpyra build examples/score
+      - run: anpyra verify examples/score/build/dev.anpyra.score.apk
+      - run: python -m pip wheel --no-deps . --wheel-dir dist

anpyra-0.1.0/.gitignore

@@ -0,0 +1,227 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$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
+*.lcov
+.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
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.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
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs/Zensical 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/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore that
+#   can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, you
+#   could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# Anpyra local inputs and signing state
+.reference/
+.anpyra/
+.pyandroid/
+*.apk
+*.dex

anpyra-0.1.0/CHANGELOG.md

@@ -0,0 +1,51 @@
+# 📝 Changelog
+
+This file records user-visible milestones. Planned work belongs in the [roadmap](docs/roadmap.md), not as completed release notes.
+
+## 🛠️ Unreleased
+
+### 📦 Python package publishing
+
+- Manual tagged TestPyPI/PyPI workflow with reusable CI, version guards, archive/README checks and isolated wheel build smoke test.
+- Separate least-privilege publishing job using Trusted Publishing and checked build artifacts.
+- Package classifiers/project links and a dedicated PyPI-compatible README.
+- Read-only release validator, focused rejection tests and complete account/tag/command guide.
+- Workflow prepared locally; trusted-publisher configuration and first index upload remain pending.
+
+### 🌍 Native platform organization
+
+- Shared source analysis/IR, identity metadata and project paths moved to `common/`.
+- Android authoring/config, DEX, manifest, APK packaging/signing/verification moved to `platforms/mobile/android/`.
+- Reserved native iOS and Windows/macOS/Linux backend packages; no additional target implemented.
+- Native registry, `targets` command and `build`/`check --target`; Android remains the default and planned targets fail before writes.
+- Historical imports preserved through forwarding modules; seven additional boundary/dispatch/compatibility checks.
+- Updated ownership guides, source reference and future native backend phase. Web is outside target scope.
+
+### 📚 Documentation
+
+- Recommend uv for installation, retain pip alternatives and document activation-free setup and wheel workflows.
+- Clarify that Android builds use Python dependencies without Java/JDK, Kotlin, Android SDK/NDK or Android Studio; adb remains optional.
+- Document emoji prefixes for every new commit subject.
+
+- Modern project README with navigation, badges, pipeline, supported feature summary and alpha limits.
+- Detailed user/developer guides, file/function map, debugging and extension workflows.
+- Full phase roadmap distinguishing implemented work from pending device validation and future features.
+- Contribution, issue/PR templates and walkthroughs for both examples.
+
+### 🗂️ Organization and checks
+
+- Existing tests grouped into unit/integration/regression without changing public framework module paths.
+- Historical fixtures retained; discovery markers added for grouped tests.
+- Documentation link/title/Python-example checks and CI integration.
+- Source-distribution inclusion of documentation, examples, tests and repository maintenance files.
+
+## 📦 0.1.0 — October 4, 2026
+
+- Unified the PyAndroid 001–008 work around the cumulative experiment 008 compiler.
+- Added installable package, typed authoring imports, project configuration and compile/build APIs.
+- Added six CLI commands, example projects, JSON build report and v2 APK verification.
+- Retained per-project debug signing identity and deterministic package metadata.
+- Added 41 host tests, Ruff checks and Windows/Linux CI configuration.
+- Built/verified both examples and tested isolated wheel installation/new-app build.
+
+The baseline is alpha. Original experiment device success was reported by the author; framework-specific phone acceptance and independent binary inspection remain pending. There is no full Python runtime, general Android binding surface, release identity workflow or publishing service in this version.

anpyra-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# 🤝 Contributing to Anpyra
+
+Anpyra is an alpha native compiler framework. Contributions should make one concrete behavior clearer, more reliable, or more useful without claiming unsupported Python/Android features.
+
+## 🧭 Find your starting point
+
+- Users: begin with the [user guide](docs/user_guide/README.md).
+- Maintainers: read [development setup](docs/developer_guide/development_setup.md) and [source reference](docs/developer_guide/source_reference.md).
+- Feature proposals: check [roadmap phases](docs/roadmap.md).
+- Bug reports: use [troubleshooting](docs/user_guide/troubleshooting.md) and [debugging](docs/developer_guide/debugging.md).
+
+## 🐛 Report a bug
+
+Provide expected/actual behavior, exact command, minimal app source/config, host versions and complete error. For Android issues, include device/API and install/launch results. A redacted IR/Dalvik excerpt or report helps; private signing keys and unrelated device logs do not belong in an issue.
+
+The [bug report template](.github/ISSUE_TEMPLATE/bug_report.md) provides those fields. State whether the source is documented as supported; an unsupported feature request is a different discussion from broken existing behavior.
+
+## 🧩 Propose a feature
+
+Describe the concrete app you want to build, minimal syntax/API, expected Android behavior, roadmap phase and acceptance criteria. Explain compiler/IR/backend/package impact using the [extension guide](docs/developer_guide/extending.md). Avoid making the front end accept a feature before code generation exists.
+
+## 🏗️ Prepare a change
+
+1. Create a descriptive branch and establish passing baseline checks.
+2. Reproduce the problem with a focused test or concrete documented example.
+3. Make the smallest coherent change across necessary stages.
+4. Put unit/integration/historical regression checks in their matching groups.
+5. Update user/developer guides if behavior, paths or limits change.
+6. Run relevant checks and describe their results honestly.
+
+```powershell
+python -m pip install -e ".[dev]"
+python -m unittest discover -s tests -v
+ruff check src tests examples scripts
+ruff format --check src tests examples scripts
+python scripts/check_docs.py
+git diff --check
+```
+
+For runtime or binary-format changes, follow [device/release validation](docs/developer_guide/testing.md). A docs-only change needs link/example checks; relocating tests also needs complete discovery and example smoke checks.
+
+## 🧹 Repository conventions
+
+Use `src/` for runtime code, `examples/` for complete application projects, `tests/` for evidence, `docs/user_guide/` for user tasks and `docs/developer_guide/` for internals. Keep documentation in simple English with meaningful emoji headings and relative file links.
+
+Do not commit generated APKs/DEX, local environments, caches, or debug/release keys. Preserve experiment fixtures as historical inputs. Maintain public import compatibility deliberately and record any breaking behavior in the changelog.
+
+## 💬 Commit messages
+
+Every new commit subject must begin with a meaningful emoji and describe the concrete change. Use `🐛` for fixes, `✨` for features, `📚` for documentation, `♻️` for refactoring, or `🧪` for tests. For example: `📚 Recommend uv and clarify Android build requirements`.
+
+Apply this convention to new commits without rewriting existing published history.
+
+## 📝 Review description
+
+Use the [PR template](.github/pull_request_template.md). Explain the original problem, resulting behavior, affected stages, validation, compatibility and remaining limitations. Distinguish tests you ran from CI/device checks still pending. Keep roadmap completion tied to actual evidence.
+
+The repository uses [Apache-2.0](LICENSE); preserve relevant notices when modifying existing code.