indygreg / indygreg/PyOxidizer
Trouble running Rust project
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
I have been scouring the docs, code, and build.rs files for a while trying to figure out of I'm doing something incorrectly. After cargo install pyoxidizer I created a new rust project via pyoxidizer init-rust-project newproject, I added jemalloc to the default features. However, when I try cargo run --release everything builds but it just sits there not proceeding past the call to MainPythonInterpreter::new(config). Logging before this call is fine, but it never seems to get past it.
I tried using a custom PythonConfig as described in the book but no matter what I've done I cannot get past the ModuleNotFoundError: No module named 'encodings' error.
I have attempted this on Debian 10 and Arch with the same results. Hopefully I'm just missing something simple.
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 issue with cargo install pyoxidizer, pyoxidizer init-rust-project newproject, and cargo run --release on a supported environment. Start by reading the generated build.rs, the MainPythonInterpreter::new(config) call, and the linked PythonConfig documentation. Done means the project starts past initialization without hanging or reporting ModuleNotFoundError: No module named 'encodings'.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100