indygreg / indygreg/PyOxidizer
Edit-build-run loop when modifying Python is a bit cumbersome
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
Every time I modify Python code, if I want it to be included in the build while testing, I have to delete build and do cargo clean or the new modifications aren't picked up.
Is there a cleaner approach?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the edit-build-run loop described in the issue, comparing a normal build with one after modifying Python code. Start by tracing how the build handles Python changes and cargo clean; done means updated Python is included without manually deleting build or running cargo clean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100