indygreg / indygreg/PyOxidizer
Reading/Importing non-python files
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
Is there a strategy for importing/reading files that are not python but other formats? For example, say I have values to read in from a config.txt file. What is the packaging strategy around that and is it possible to bundle these intelligently into the exe or should I be using the `app-relative` configuration option?
I am currently using the `app-relative` configuration option, but that requires be to be in the containing folder of the binary to use it which is not convenient. If anyone has an elegant way they are solving this I would be interested to hear.
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 by reviewing PyOxidizer's packaging and configuration behavior for a non-Python file such as config.txt, with particular attention to the app-relative option. Done means establishing whether such files can be bundled into the executable and documenting or implementing a practical strategy that does not require running from the binary's containing folder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100