Allow the use of a `.env` file with the generated program to set environment variables
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
This would be particularly useful to set PYAPP_INSTALL_DIR_<project> for a given project automatically. For instance, I could give the generated executable and a .env file that specifies that the target directory is a subdirectory of the current working directory -- e.g., "./some_dir" - which would make it easier to have control over where the target is unpacked and run from.
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 examining how the generated program currently reads environment variables, especially PYAPP_INSTALL_DIR_. Determine the expected .env location and parsing behavior, then verify that a generated executable plus a .env file can set the target directory as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100