Make Rust the sole pack builder and remove the Python pack path

Open
  • Is something wrong?
#562 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
12/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
godot, python, rust
Domain
build-system, tooling

Research direction

This is a child task of a larger parent issue and depends on unlanded coverage PRs and a paused palette task, so it cannot start yet. Begin by reading the Python pack entry point and its parity tooling alongside the Rust pack builder that the package and setup screen already call (psiv-pack). Done means whole-pack JSON/binary parity and decoded-PNG parity are recorded, the Python pack path and its CI jobs are removed, and the full gate and native release builds pass.

Written by the indexing model from the issue text.

Description

later

Child of https://github.com/TusanHomichi/PSIV/issues/115. Finish only this task in one fresh session and one PR. The parent's original authorization boundaries still apply; this child grants no additional authority. Do not read earlier sessions' transcripts.

Depends on the preceding coverage PRs and lifting the palette pause. Complete #216's final switch in one PR: first prove whole-pack parity at the candidate revision, then remove the Python pack entry point and pack-only modules/tests, parity tooling and obsolete CI jobs. Port or retire remaining consumers of deleted modules and update affected documentation. Preserve independent research tooling. The package and setup screen already use psiv-pack; retain their interface. Publish nothing and commit no ROM-derived evidence.

Verification: Record final pre-deletion JSON/binary equality and existing decoded-PNG parity, plus full-pack timing. After deletion, run the full applicable gate and native release builds. Verify no live Python pack caller or broken import remains.

If this is too big, publish any progress, split it with proj split FILE (a JSON array of title/body/check tasks), then end the session. Wait for the PR to land before declaring this task done.

Dominant language
Rust
Stars
1
Forks
0
Avg merge
8h 43m
Merged PRs (30d)
288

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TusanHomichi/PSIV

All issues in TusanHomichi/PSIV

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.