indygreg / indygreg/PyOxidizer
Module search location fallback option
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
PC: Windows 10
Pyoxidizer 0.10:pre
It seems when compiling with numpy it breaks the previous import of a script as module to run from "in-memory". Script must now be copied to lib. Also all other pip installed modules have to be imported from lib now as well, I believe due to: python_config.module_search_paths = ["$ORIGIN/lib"]
Instead can a module_search_paths_fallback be used to run rest of imports normally from memory and then when it gets to numpy searching memory and then lib/ setting this manually instead for modules we know need __file__.
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
No source files or tests are named. Start by tracing the python_config.module_search_paths setting and the in-memory import behavior described in the report, then reproduce it with numpy and other pip-installed modules. Done means a documented fallback option supports normal in-memory imports while locating modules such as numpy from lib when needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python, rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100