indygreg / indygreg/PyOxidizer
Error when running `pyoxidizer run` on a python3.7 project
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
When I try to run `pyoxidizer run` within a virtualenv I get this error:
```
thread 'main' panicked at 'unable to get directory entry: Error { depth: 0, inner: Io { path: Some("./env/lib/python3.9/
site-packages"), err: Os { code: 2, kind: NotFound, message: "No such file or directory" } } }', /home//.carg
o/registry/src/github.com-1ecc6299db9ec823/python-packaging-0.11.0/src/filesystem_scanning.rs:117:35
```
Why is it looking for python3.9?
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 `pyoxidizer run` and `python-packaging-0.11.0/src/filesystem_scanning.rs:117`, then inspect how the virtualenv interpreter and site-packages path are selected. Reproduce the error in a Python 3.7 virtualenv and determine why scanning targets `./env/lib/python3.9/site-packages`; done means the command uses the environment's actual path without panicking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100