indygreg / indygreg/PyOxidizer
run_code dropped from pyembed 10.3
Open
Nobody has claimed this yet.
question
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
run_code has been removed for perfectly good reasons, but :
- the run_code is still in documentation : https://pyoxidizer.readthedocs.io/en/stable/rust_rust_code.html
- how to call python code from rust ? Does PyOxidizer focus on being a tool to package python code, and drop the idea of also being a tool to embed python in rust application, and a bridge from the former to the later ?
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 with the Rust/Python embedding documentation at rust_rust_code.html and compare its run_code guidance with pyembed 10.3. Confirm which embedding workflow is supported, then update the documentation to remove obsolete guidance and clearly state PyOxidizer’s scope; completion means the page matches the current release and answers how to call Python from Rust.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100