indygreg / indygreg/PyOxidizer
How to rebuild the binary?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
Apologies if this already exists in the docs, but is there a quick way to rebuild the binary after changing Python files using either the `virtualenv` or `setup-py-install` packaging rules?
If I run `build` a second time, it doesn't seem to pull in the new Python files. I've just been deleting the `build` directory to get it to rebuild, but that is slow and seems to result in more work than needed.
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
Start by examining the virtualenv and setup-py-install packaging rules and the behavior of a second build after a Python file changes. Verify whether the build directory is expected to be removed, then document the quickest supported rebuild workflow and its expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100