You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
python-dotenv has a feature called find_dotenv(), which -
will try to find a .env file by (a) guessing where to start using file or the working directory -- allowing this to work in non-file contexts such as IPython notebooks and the REPL, and then (b) walking up the directory tree looking for the specified file
This is specially useful for zipapps made using shiv. I don't want to package my sensitve info inside the zipapp, but python-decouple can't find my .env when I run the zipapp, because it only looks at the __file__, not current directory. (correct me if i'm wrong)
Thanks!
The text was updated successfully, but these errors were encountered:
devxpy
changed the title
[Feature Request] Port find_dotenv feature from python-dotenv
[Feature Request] Port find_dotenv() feature from python-dotenv
Sep 25, 2018
On the UX side, would you prefer including this as an improvement over the regular .env finder in this project, or as a separate function, like in python-dotenv?
python-dotenv has a feature called
find_dotenv()
, which -This is specially useful for zipapps made using shiv. I don't want to package my sensitve info inside the zipapp, but python-decouple can't find my
.env
when I run the zipapp, because it only looks at the__file__
, not current directory. (correct me if i'm wrong)Thanks!
The text was updated successfully, but these errors were encountered: