thoughtbot / thoughtbot/dotfiles
Python3 os.getenv Failed to Gather Environment Variable During Runtime
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.2k
- Forks
- 1.8k
- Avg merge
- 10d 14h
- Merged PRs (30d)
- 1
Description
Howdy!
Ventura 13.4 using zsh.
I was using the dotfiles and followed all the steps including creating some custom dotfiles-local/ of my own. Whatever file I export an environment variable to any file such as
~/.bash_profile~/.zshrc@~/.zprofile@~/.env
Upon adding the environment variable's, I also started a fresh terminal and used rcup from ~/. Via os.getenv with Python3 does not seem to be able to verify it's existence. Though I don't think its soley related to os.getenv as when I export, I never see the variable listed either.
Which dir/file should I be using to store local environment variable's with this setup?
Thank you so much for your awesome contributions 🙏🏼
TYIA!
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 the dotfiles setup instructions and how rcup handles dotfiles-local/, then reproduce the report with the listed zsh startup files and Python 3 os.getenv. Determine which supported location is intended for local environment variables and confirm that the variable is available in a fresh terminal and to Python.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, shell, zsh
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100