ci: add Python CI workflow for trinity_wallet_py

[Copilot]

The C/C++ workflow runs ./configure on all pushes/PRs without path filtering, causing failures on Python-only changes (example).

Changes

• Add .github/workflows/python-package.yml with path filter trinity_wallet_py/**
• Workflow runs Python 3.11, installs dependencies from requirements.txt, executes tests via pytest
• Future Python-only changes trigger Python CI only, not C/C++ CI

on:
  push:
    branches: [ "master" ]
    paths:
      - "trinity_wallet_py/**"
  pull_request:
    branches: [ "master" ]
    paths:
      - "trinity_wallet_py/**"

The C/C++ workflow at a0c716da remains unchanged and will continue running for non-Python changes.

Original prompt

Add a GitHub Actions workflow to run CI for the Python package trinity_wallet_py and restrict triggers so it only runs for changes under trinity_wallet_py/**.

Background and rationale:

• A previous CI failing job indicates the C/C++ workflow was triggered for a Python-only change and failed because it runs ./configure. Reference failing job: https://github.com/Action-Committee/Trinity_py/actions/runs/20143292221/job/57817586867
• The C/C++ workflow that caused the failure is at: https://github.com/Action-Committee/Trinity_py/blob/a0c716da4774aa93b1a28705d662bfa6a7ebabe3/.github/workflows/c-cpp.yml (use ref a0c716d for links).
• The repository contains a Python package at trinity_wallet_py with requirements.txt and test_wallet.py which should have their own CI workflow.

Required change (one file):

• Create file .github/workflows/python-package.yml with the exact YAML content below.

File contents (exact, verbatim):

name: Python package CI

on:
push:
branches: [ "master" ]
paths:
- "trinity_wallet_py/"
pull_request:
branches: [ "master" ]
paths:
- "trinity_wallet_py/"

jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: '3.11'
- name: Cache pip
uses: actions/cache@v4
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('trinity_wallet_py/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
- name: Install dependencies
run: |
python -m pip install --upgrade pip
if [ -f trinity_wallet_py/requirements.txt ]; then
pip install -r trinity_wallet_py/requirements.txt
fi
- name: Run tests
run: |
python -m pip install pytest || true
pytest -q trinity_wallet_py/test_wallet.py

Commit & PR details:

• Branch name: ci/add-python-workflow
• Commit message: ci: add Python CI workflow for trinity_wallet_py
• PR title: ci: add Python CI workflow for trinity_wallet_py
• PR body: Adds a GitHub Actions workflow that runs tests for trinity_wallet_py and restricts triggers to trinity_wallet_py/** so the C/C++ CI (which runs ./configure) isn't triggered for Python-only changes. References: failing job https://github.com/Action-Committee/Trinity_py/actions/runs/20143292221/job/57817586867 and C/C++ workflow https://github.com/Action-Committee/Trinity_py/blob/a0c716da4774aa93b1a28705d662bfa6a7ebabe3/.github/workflows/c-cpp.yml
• Merge strategy: create PR and merge into master (merge commit). Delete branch after merge.

Do NOT modify any other files in the repository. Please create the branch, add the file, open the PR targeting master, wait for all checks to complete, then merge the PR, and delete the branch.

This pull request was created as a result of the following prompt from Copilot chat.

Add a GitHub Actions workflow to run CI for the Python package trinity_wallet_py and restrict triggers so it only runs for changes under trinity_wallet_py/**.

Background and rationale:

• A previous CI failing job indicates the C/C++ workflow was triggered for a Python-only change and failed because it runs ./configure. Reference failing job: https://github.com/Action-Committee/Trinity_py/actions/runs/20143292221/job/57817586867
• The C/C++ workflow that caused the failure is at: https://github.com/Action-Committee/Trinity_py/blob/a0c716da4774aa93b1a28705d662bfa6a7ebabe3/.github/workflows/c-cpp.yml (use ref a0c716d for links).
• The repository contains a Python package at trinity_wallet_py with requirements.txt and test_wallet.py which should have their own CI workflow.

Required change (one file):

• Create file .github/workflows/python-package.yml with the exact YAML content below.

File contents (exact, verbatim):

name: Python package CI

on:
push:
branches: [ "master" ]
paths:
- "trinity_wallet_py/"
pull_request:
branches: [ "master" ]
paths:
- "trinity_wallet_py/"

jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: '3.11'
- name: Cache pip
uses: actions/cache@v4
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('trinity_wallet_py/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
- name: Install dependencies
run: |
python -m pip install --upgrade pip
if [ -f trinity_wallet_py/requirements.txt ]; then
pip install -r trinity_wallet_py/requirements.txt
fi
- name: Run tests
run: |
python -m pip install pytest || true
pytest -q trinity_wallet_py/test_wallet.py

Commit & PR details:

• Branch name: ci/add-python-workflow
• Commit message: ci: add Python CI workflow for trinity_wallet_py
• PR title: ci: add Python CI workflow for trinity_wallet_py
• PR body: Adds a GitHub Actions workflow that runs tests for trinity_wallet_py and restricts triggers to trinity_wallet_py/** so the C/C++ CI (which runs ./configure) isn't triggered for Python-only changes. References: failing job https://github.com/Action-Committee/Trinity_py/actions/runs/20143292221/job/57817586867 and C/C++ workflow https://github.com/Action-Committee/Trinity_py/blob/a0c716da4774aa93b1a28705d662bfa6a7ebabe3/.github/workflows/c-cpp.yml
• Merge strategy: create PR and merge into master (merge commit). Delete branch after merge.

Do NOT modify any other files in the repository. Please create the branch, add the file, open the PR targeting master, wait for all checks to complete, then merge the PR, and delete the branch.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.