An env var that disables path recompilation triggers.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
I would really love an environment var that disables all recompilation triggers of PyO3.
Currently I often patch pyo3 to prevent these recompilations.
I found it impossible to keep my path variable consistent in my flow, and given that pyo3 is used deep in our stack, this often triggers full 4/5min recompilations.
I know that the recompilations are done to prevent gnarly, bugs so I would document that env var (maybe not document at all) as "only use when you know what you are doing". Changes of paths, need to be followed up with a cargo clean.
Contributor guide
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 reviewing the referenced PyO3 commit and tracing the current recompilation triggers in the repository. Determine where an environment-variable escape hatch would be integrated, then verify that it suppresses those triggers and document the warning that path changes should be followed by 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
- Mostly clear
- Newbie friendliness
- 35/100